Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read options from .aws/config in addition to .aws/credentials #10546

Closed
cyberduck opened this issue Nov 29, 2018 · 2 comments
Closed

Read options from .aws/config in addition to .aws/credentials #10546

cyberduck opened this issue Nov 29, 2018 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Nov 29, 2018

ef2b6bd created the issue

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 29, 2018

@dkocher commented

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).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 29, 2018

@dkocher commented

"Found the legacy config profiles file at [/aws/config]. Please move it to the latest default location [/.aws/credentials]."

Loading

@cyberduck cyberduck closed this May 31, 2019
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants