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
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: