ECS container credentials #281
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This seems pretty straight forward to me. @geemus mind giving it a look ? |
|
👍 Thanks! |
|
@geemus Any chance you could cut a release with these changes? |
|
Thanks! On Thu, Aug 4, 2016 at 10:40 AM, Josh Lane notifications@github.com wrote:
|
|
Thanks! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for ECS task container credentials/roles.
Docs: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html
aws-sdk PR: aws/aws-sdk-ruby#1243
I used the same algorithm as aws-sdk for choosing when to use the ECS creds. I don't love the
options[:metadata_connection]but we have to connect to a different host to get the region when using ECS creds.