-
Notifications
You must be signed in to change notification settings - Fork 249
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
AWS credentials file keys should not be case sensitive #1020
Comments
Today same case with me but this thing was highlighted by rust-analyzer. |
This will be fixed in smithy-lang/smithy-rs#3344, thanks for reporting! |
## Motivation and Context - https://github.com/aws/aws-sdk/issues/574 - awslabs/aws-sdk-rust#1020 ## Description To match the CLI behavior and improve customer experience, make the keys on the profile file case-insensitive. ## Testing - New credentials integration test ## Checklist <!--- If a checkbox below is not applicable, then please DELETE it rather than leaving it unchecked --> - [x] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates - [x] I have updated `CHANGELOG.next.toml` if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
fixed in the latest version of aws-config |
|
@rcoh Nice, thanks |
Describe the bug
The AWS SDK for Rust requires lowercase keys, such as
aws_access_key_id
instead ofAWS_ACCESS_KEY_ID
. This is inconsistent with the AWS CLI, and I'm 90% confident other SDKs don't have this limitation either.Expected Behavior
AWS credentials file should support case insensitive configuration keys.
Current Behavior
AWS SDK for Rust requires lower-case keys in the AWS credentials file.
Reproduction Steps
Possible Solution
Make the profile file credentials chain case insensitive.
Additional Information/Context
No response
Version
The text was updated successfully, but these errors were encountered: