-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/aws: Provide a better message if no AWS creds are found #4869
Conversation
catsby
commented
Jan 27, 2016
👍 aws/aws-sdk-go#512 should allow us to give users more details about where the credentials come from - helpful for further debugging. I'll probably send something in a separate PR. |
`AWS_SECRET_ACCESS_KEY` environment variables. Lastly, if those are not found | ||
it will look for credentials in the default location for a credentials file, or | ||
the file path specified in the `shared_credentials_file` attribute of the | ||
`provider` block. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The shared credentials path can be overridden with AWS_SHARED_CREDENTIALS_FILE
And the creds file can have multiple profiles, which can be selected via profile
, which can also be set via AWS_PROFILE
.
I wonder if this would look clearer as a numbered list of "things we check in this order" than a prose paragraph?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this would look clearer as a numbered list of "things we check in this order" than a prose paragraph?
probably, will do
Big 👍 for getting a link to website docs in this error message - that way we can continue to improve that message as we learn more about what's helpful to users. Made some comments on the initial contents of the website message above inline. |
LGTM |
provider/aws: Provide a better message if no AWS creds are found
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |