-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Ignore capitalization of aws_access_key_id and aws_secret_access_key elements in credentials file #2458
Comments
Thanks for reaching out. According to the design specification for this feature (written for SDKs and published internally) it does not specifically mention that these keys should be case insensitive. CLI may have broken that specification at some point and must continue to support it. I'll check with other teams on this. Is there a specific need to be case insensitive? You should be able to define these in lower case and it will work for both CLI and SDKs. Historically, we get many "CLI does this, why don't you?" type requests and they're not always the correct thing to do. |
Using all lowercase for the credentials is the correct solution, it just caught me off guard. I can agree that this is indeed one of those |
|
Understood, and makes sense. I think that the specification we have can be amended to mention CLI's behavior or be broadened to case sensitive keys. I will follow up with that. |
For the ones who stumbled on this issue and still would like to see it supported, we are tracking a cross-SDK feature request here: aws/aws-sdk-java-v2#5689. |
Is your feature request related to a problem? Please describe.
The SDK does not behave the same way as the AWS CLI when reading credentials from the
~/.aws/credentials
file in regards to the capitalization of theaws_access_key_id
andaws_secret_access_key
keys.Example
The SDK will read this credential properly.
The SDK will not read this credential as
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
are capitalized, though the AWS CLI will still read this credential properly.Describe the solution you'd like
I would like the SDK to read credentials from the
~/.aws/credentials
file regardless of their capitalization.Describe alternatives you've considered
The alternative is simple enough in that using only all lower case keys in
~/.aws/credentials
is the solution, however, this tripped me up for a bit when using a downstream dependency of the SDK.[x] 👋 I may be able to implement this feature request
Additional context
The text was updated successfully, but these errors were encountered: