-
Notifications
You must be signed in to change notification settings - Fork 449
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
new feature: support AWS Container credential provider #4903
Comments
Hi, @Samrose-Ahmed, does this issue related to #4964? |
Yes it's the same. |
Thank you! I will redirect the discussion here. |
Hi, @Samrose-Ahmed, I expect to add this feature in our next release. |
General question regarding this, would it be a good idea to wrap the AWS SDK with the credentials provider to do this job? This has been my current workaround for this issue and might be a better long-term solution for managing all the various ways you can authenticate with AWS. |
Thanks for the suggestion. We previously had a discussion here: #139. The various methods for authentication are limited and rarely change, so we can ultimately support them all. I believe it isn't worth introducing the AWS SDK for authentication. |
Feature Description
via
AWS_CONTAINER_CREDENTIALS_RELATIVE_URI
environment variable in ECS/container settings: see https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.htmlProblem and Solution
load credentials in ecs environment
Additional Context
No response
Are you willing to contribute to the development of this feature?
The text was updated successfully, but these errors were encountered: