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
I have noticed quite an annoying issue with the current implementation of S3 + STS + mfa token.
It is working but only if all the config is inside .aws/credentials and ignores totally .aws/config.
This goes against how the AWS cli is implemented.
AFAIK .aws/credentials is only supposed to contain the keypair and .aws/config is where the source_profile, mfa_serial, role_arn is stored. Cyberduck is only working if all the information is stored inside .aws/credentials.
Gregory
The text was updated successfully, but these errors were encountered:
The AWS CLI uses two files to keep the sensitive credential information (in ~/.aws/credentials) separated from the less sensitive configuration options (in ~/.aws/config).
Hi,
I have noticed quite an annoying issue with the current implementation of S3 + STS + mfa token.
It is working but only if all the config is inside .aws/credentials and ignores totally .aws/config.
This goes against how the AWS cli is implemented.
AFAIK .aws/credentials is only supposed to contain the keypair and .aws/config is where the source_profile, mfa_serial, role_arn is stored. Cyberduck is only working if all the information is stored inside .aws/credentials.
Gregory
The text was updated successfully, but these errors were encountered: