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

How to provide AWS profile or credentials? #15

Open
carlkibler opened this issue Sep 30, 2022 · 2 comments
Open

How to provide AWS profile or credentials? #15

carlkibler opened this issue Sep 30, 2022 · 2 comments
Assignees
Labels
awaiting feedback enhancement New feature or request
Milestone

Comments

@carlkibler
Copy link

Describe the bug
It is unclear to me how to specify the named AWS profile to use, or if not supported, could it be?
My team uses numerous AWS accounts: dev-1, dev-2, prod, devops, etc. Each has an AWS profile stored in ~/.aws/ files. So with AWS cli and most tools we can specify --profile dev- and the proper credentials are loaded.

Expected behavior
Specified profile is used. Of course, fallback to whatever the current default behavior is, but I can't tell what that is either. A note in the readme would help!

@carlkibler carlkibler added the bug Something isn't working label Sep 30, 2022
@soapiestwaffles
Copy link
Owner

ah, yes, you should be able to use the environment variable AWS_PROFILE and set it to the name of your target profile from your credentials file.

As as side node, adding a --profile to the parameters as well isn't a bad idea! I'll add that feature.

@soapiestwaffles
Copy link
Owner

I will also add that info into the README!

@soapiestwaffles soapiestwaffles added this to the 1.2.0 milestone Oct 1, 2022
@soapiestwaffles soapiestwaffles removed the bug Something isn't working label Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

2 participants