Add support for Web Identity credentials #1
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The default chain credential provider in Rusoto doesn't currently support Web Identity (needed for workloads running as pods on EKS using service accounts to obtain IAM credentials).
This pull request adds support on top of the Rusoto work to add it as a provider in the expected order (it needs to be able to get credentials from WebIdentity before the IMDS provider as the EKS worker node will have IAM creds for cluster management stuff but it still allows for the credentials to be overridden by the
AWS_ACCESS_KEY_IDetc environment variables).