-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Not so forthcoming/consistent error when aws credentials are not provided in an assume role scenario #2763
Comments
I believe this occurs when a profile references a source profile that has no credentials.
The error message is definitely not very helpful. I'll see what we can do to improve this. Blind check is here. |
The same error occurs, if for some reason the |
This appears to be a duplicate of #2060. When I assumed a role without s3 permissions and attempted the s3 ls command I received this error: And @dschneller issues with credentials file ownership is also captured here: #2565. I think we should close this and continue any discussion in those open issues. |
|
I am running from the brew install version of awscli that points to head on a Mac (installed via brew install awscli --HEAD) as of this morning.
When attempting to verify my AWS credentials (but with my credentials not provided), I get a helpful error...
However, when trying to do something else with the awscli, I get a rather brief indication of what might be the issue, but it's not very direct...
If we run the same command with --debug, we can get the full stack trace...
The text was updated successfully, but these errors were encountered: