Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(credential-provider-imds): support ECS and EKS credential uris #1144

Closed
wants to merge 2 commits into from

Conversation

armsnyder
Copy link

closes #1143

I added more allowed hostnames for the AWS_CONTAINER_CREDENTIALS_FULL_URI environment variable. These allowed hostnames match the ones allowed by the official Go SDK. See: https://github.com/aws/aws-sdk-go-v2/blob/a7db10670faedd542dc92cec6d0c602e5315a3a9/config/resolve_credentials.go#L33-L52

Note that I have not tried deploying an app to EKS with this build of @smithy/credential-provider-imds, so I do not know for certain if this is the only issue that is preventing the use of EKS Pod Identities on EKS.

@armsnyder armsnyder requested review from a team as code owners January 14, 2024 21:57
@armsnyder armsnyder changed the title 1143 eks credential feat(credential-provider-imds): support ECS and EKS credential uris Jan 14, 2024
@kuhe
Copy link
Contributor

kuhe commented Feb 27, 2024

this should no longer be necessary, since the AWS SDK has been updated to look for credentials from the new sources.

Use v3.515.0 or higher of the JSv3 AWS SDK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Credentials from EKS Pod Identity causing error
2 participants