Auth Error With No Default Credentials #139
Comments
|
You can select which profile to use by using |
BTripp1986
added a commit
to BTripp1986/aiodynamo
that referenced
this issue
Dec 18, 2022
this behavior is more in line with the behavior expected by users coming from boto3 or aiobotocore. [Issue HENNGE#139]
BTripp1986
added a commit
to BTripp1986/aiodynamo
that referenced
this issue
Dec 21, 2022
this behavior is more in line with the behavior expected by users coming from boto3 or aiobotocore. [Issue HENNGE#139]
BTripp1986
added a commit
to BTripp1986/aiodynamo
that referenced
this issue
Dec 22, 2022
this behavior is more in line with the behavior expected by users coming from boto3 or aiobotocore. [Issue HENNGE#139]
BTripp1986
added a commit
to BTripp1986/aiodynamo
that referenced
this issue
Dec 26, 2022
this behavior is more in line with the behavior expected by users coming from boto3 or aiobotocore. [Issue HENNGE#139]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have access to several AWS accounts via SSO and no default profile for AWS. When I sign in to AWS via SSO the
.aws/credentialsfile is updated with a fresh Access Key, Secret Key, and Security Token.I specify which credentials I will use with the
AWS_PROFILEenv var, which is checked as part of the credentials chain lookup. If using boto3 or the aws-cli this method works. With this method I can sign in via SSO to dev and prod accounts. Then if IAWS_PROFILE=dev aws s3 ls(or similar call in boto3) it will run the command against the dev account. Then if IAWS_PROFILE=prod aws s3 lsit will run against prod.This doesn't seem to work with aiodynamo. In order to get it to work I need to create a default profile and then copy/paste the credentials from the desired profile into the default profile. Aiodynamo should respect the
AWS_PROFILEenv var.The text was updated successfully, but these errors were encountered: