This repository has been archived by the owner on May 18, 2021. It is now read-only.
setting AWS_PROFILE as part of exec leads to errors in some apps: #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Some apps (for example, packer) use the AWS_PROFILE setting to determine which profile to load out of ~/.aws/config shared config. The problem is that these profiles don't have associated credentials, so those applications fail. Instead, don't set profile, and the applications just use the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY vars.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
determine which profile to load out of ~/.aws/config shared config.
The problem is that these profiles don't have associated
credentials, so those applications fail. Instead, don't set
profile, and the applications just use the AWS_ACCESS_KEY_ID and
AWS_SECRET_ACCESS_KEY vars.