-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Panic when using EcsContainer and AWS_CONTAINER_CREDENTIALS_FULL_URI #4572
Comments
rnett
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Sep 27, 2022
RanVaknin
added
p3
This is a minor priority issue
queued
This issues is on the AWS team's backlog
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Nov 29, 2023
Comments on closed issues are hard for our team to see. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
According to the AWS docs
AWS_CONTAINER_CREDENTIALS_FULL_URI
should be used whenAWS_CONTAINER_CREDENTIALS_RELATIVE_URI
is not set. However the SDK does not seem to do this. Instead, it panics.Expected Behavior
When
EcsContainer
is used as the credential source butAWS_CONTAINER_CREDENTIALS_RELATIVE_URI
is not set, the SDK falls back to usingAWS_CONTAINER_CREDENTIALS_FULL_URI
.Current Behavior
It panics when
EcsContainer
is used as the credential source butAWS_CONTAINER_CREDENTIALS_RELATIVE_URI
is not set:Reproduction Steps
Use
eksctl
version0.112.0
on Cloud Shell with the following config in~/.aws/config
:then run
I don't expect the actual command to matter.
Possible Solution
Respect the documented behavior.
Additional Information/Context
No response
AWS Go SDK V2 Module Versions Used
Whatever
eksctl
version0.112.0
uses.Compiler and Version used
Whatever
eksctl
version0.112.0
uses.Operating System and version
Linux, 4.14.287-215.504.amzn2.x86_64 (AWS Cloud Shell)
The text was updated successfully, but these errors were encountered: