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
It appears that FileCredentials expects to see credentials at ~/.aws/credentials. However, with recent versions of the AWS CLI, this file isn't populated, for example, when authenticating via aws sso login. This behaviour change has been discussed at length here: aws/aws-cli#4982. This article discusses more about why relying on .aws/credentials isn't the right approach.
Would it be possible to update FileCredentials to leverage credential_process?
The text was updated successfully, but these errors were encountered:
You can tell FileCredentials where to look for the credentials file by passing it a path as its first argument.
credential process is unrelated to FileCredential. I would probably accept a PR that added a credentials loader that supports a credential process, but in the meantime, aiodynamo supports custom credential providers so you can write an implementation that works for you without relying on me merging a PR and releasing a new version.
It appears that
FileCredentials
expects to see credentials at~/.aws/credentials
. However, with recent versions of the AWS CLI, this file isn't populated, for example, when authenticating viaaws sso login
. This behaviour change has been discussed at length here: aws/aws-cli#4982. This article discusses more about why relying on.aws/credentials
isn't the right approach.Would it be possible to update
FileCredentials
to leveragecredential_process
?The text was updated successfully, but these errors were encountered: