Implement STS Web Identity Role credentials provider #286
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
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.
What this PR does
AWS credentials array will have STS Web Identity token provider as the first option if
AWS_ROLE_ARNandAWS_WEB_IDENTITY_TOKEN_FILEare available and non-empty in environment.Motivation
One of the common ways to provide S3 (or any AWS related service) access to a pod in EKS is to annotate k8s service account with specified IAM Role. Then AWS Web Identity token gets mounted to the pod and
AWS_ROLE_ARNandAWS_WEB_IDENTITY_TOKEN_FILEenvironment variables are provided automatically to the pod.This PR enables use of these credentials.