Open ykethan opened 1 month ago
marking as a bug. The workaround would be to rename one of the profiles
Is the expected behavior here to fail with a better error message? Or to pick a different profile? Our code is not picking one over the other, we are using whatever is resolved by the default credential provider.
Based on https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-configured-credential-process.html and the env info above that shows AWS_SDK_LOAD_CONFIG = 1
was set, this looks like expected and documented behavior of the node credential provider. If AWS_SDK_LOAD_CONFIG
is set, then the config file takes precedence over the credentials file.
how do i help with this?
Environment information
Description
From comment: https://github.com/aws-amplify/amplify-backend/issues/1510#issuecomment-2115668240
if you have 2 profiles, 1 sso profile and 1 aws account profile with the same name. The sandbox picks the profile stored in
~/.aws/config
instead of the SSO stored in~/.aws/credentials