[v2] credentials supplied by aws sso login do not conform to AWS standards
Problem
AWS documents that credentials generated by `aws configure` are stored in the standard path `~/.aws/credentials`: > The AWS CLI stores the credentials that you specify with aws configure in a local file named credentials, in a folder named .aws in your home directory. https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html This path is not utilized by credentials stored by `aws configure sso` or `aws sso login`. Other tools (like Terraform and Boto3) that rely on this standard do not function because they do not see the credentials stored in the `~/.aws/cli/cache/` JSON files. > Shared credential file (~/.aws/credentials) https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: [v2] credentials supplied by aws sso login do not conform to AWS standards
Doing this on a utility-by-utility or sdk-by-sdk basis will make for an absolutely horrid developer and user experience. The SDKs all support the AWS Shared Config file in some way. The SSO auth/cred process should also integrate through the AWS Shared Config so all SDKs and all utilities are able to leverage it the same way.
Trust Score
7 verifications
- 1
Doing this on a utility-by-utility or sdk-by-sdk basis will make for an absolute
Doing this on a utility-by-utility or sdk-by-sdk basis will make for an absolutely horrid developer and user experience.
- 2
The SDKs all support the AWS Shared Config file in some way. The SSO auth/cred p
The SDKs all support the AWS Shared Config file in some way. The SSO auth/cred process should also integrate through the AWS Shared Config so all SDKs and all utilities are able to leverage it the same way.
Validation
Resolved in aws/aws-cli GitHub issue #4982. Community reactions: 30 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep