You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aws::Auth::STSProfileCredentialsProvider only looks at ~/.aws/config when trying to look up a profile, but the aws_access_key_id and aws_secret_access_key are conventionally stored in ~/.aws/credentials. This causes applications using this provider to fail to acquire credentials, while applications built using other SDKs and the AWS CLI correctly find credentials.
Expected Behavior
Aws::Auth::STSProfileCredentialsProvider should read keys from ~/.aws/credentials when looking for a named profile.
Current Behavior
Aws::Auth::STSProfileCredentialsProvider will only read keys from ~/.aws/config when evaluating a profile.
Reproduction Steps
The below code tells STSProfileCredentialsProvider to load credentials from the profile in argv[1], and then print the count of buckets in an s3:ListBuckets call:
With aws_access_key_id and aws_secret_access_key in ~/.aws/credentials, this code will print 0 buckets. It will list the correct number of buckets if the key fields are instead set in ~/.aws/config.
Possible Solution
STSProfileCredentialsProvider should read the ~/.aws/credentials file when trying to load a profile.
Additional Information/Context
No response
AWS CPP SDK version used
1.9.238
Compiler and Version used
gcc 11.3.0
Operating System and version
Linux 5.15.43 on x86_64
The text was updated successfully, but these errors were encountered:
jmklix
added
p2
This is a standard priority issue
needs-review
This issue or pull request needs review from a core team member.
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Nov 18, 2022
This looks similar to this other issue: #2920
This will have to be fixed in a similar way:
Thanks for pointing this out to us. This is a problem with how the sts client was written, and will require a significant refactor of the sts client. This has been added to our backlog, but this is not something that will get completed this quarter. I don't have a timeline for when fixed, but I will update here when it does. Sorry for the delay
Describe the bug
Aws::Auth::STSProfileCredentialsProvider
only looks at~/.aws/config
when trying to look up a profile, but theaws_access_key_id
andaws_secret_access_key
are conventionally stored in~/.aws/credentials
. This causes applications using this provider to fail to acquire credentials, while applications built using other SDKs and the AWS CLI correctly find credentials.Expected Behavior
Aws::Auth::STSProfileCredentialsProvider
should read keys from~/.aws/credentials
when looking for a named profile.Current Behavior
Aws::Auth::STSProfileCredentialsProvider
will only read keys from~/.aws/config
when evaluating a profile.Reproduction Steps
The below code tells
STSProfileCredentialsProvider
to load credentials from the profile inargv[1]
, and then print the count of buckets in ans3:ListBuckets
call:With
aws_access_key_id
andaws_secret_access_key
in~/.aws/credentials
, this code will print0 buckets
. It will list the correct number of buckets if the key fields are instead set in~/.aws/config
.Possible Solution
STSProfileCredentialsProvider
should read the~/.aws/credentials
file when trying to load a profile.Additional Information/Context
No response
AWS CPP SDK version used
1.9.238
Compiler and Version used
gcc 11.3.0
Operating System and version
Linux 5.15.43 on x86_64
The text was updated successfully, but these errors were encountered: