-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Unable to locate credentials #915
Comments
Here's what I'd try:
|
@jamesls - Thanks, that helped expose my issue
|
Tried running aws configure. Gave all the details but still doesn't work for mw. I am on a mac. aws configure list |
@pranshu1992, this thread is old but I just had the same thing happen to me. I ran aws configure for a particular profile and when I ran aws configure list, my configuration list was empty (even though my .aws/ configure and connection files had values in them). To get it to work, I set the AWS_DEFAULT_PROFILE parameter on the command line to the same profile I configured and I was able to see my configuration information. |
I had the same problem with |
I had the same problem on OS X using 'aws s3 sync ...'. I'm using these files to hold AWS credentials and config:
I have no AWS environment vars set. If I rely on a default profile it will not find the credentials. This is the case if I leave off the profile switch on the command line or if I use However, if I give the profile a name other than default (in the credentials & config files) and add the command line switch '--profile profile-name' it all works fine. I'm using this as my work-around. Looks like there is an issue with handling the default profile in the credentials file. |
EDIT: It looks like this issue has a proper solution now, so there is no need to run this command with I had a similar issue to most of you. Turns out I just needed to throw in a
Then my script has the correct privileges to read from the config file. |
Is it possible not run with sudo? |
@rochapablo Yes, even with sudo the configuration files were not saving for me. Here's the solution: just change the ownership to your local user account in my case it is "jr", just replace "jr" with your username (and staff is the default group used by OSX) Example:
|
Thank you. I'm not sure what I did, but some how it started to work without the need of |
Just adding to to solution already available here: I have created default profile which solved the problem for me: My config file [default]
output=json
region=xxxxxxx and my credentials file has this [default]
aws_access_key_id=XXXXXXXX
aws_secret_access_key=XXXXXX |
@house9 - Thank you for reporting this issue. It appears the guidance provide by @jamesls and other GitHub users have ruled out a bug in the CLI. Please reply if there are any other questions or feedback on how we can improve our documentation. |
@justnance - I reported this issue on 2014-09-19, I was able to determine user error on my part a day later: 2014-09-20, I promptly closed this issue at that time, somebody else re-opened it 2 years later 2016-09-30. It is all good as far as I am concerned. |
@house9 - Thanks for the feedback. I'm glad it was resolved quickly even though the issue was reopened. |
Just in case this helps someone I wanted to add what was wrong with my aws_access_key_id=XXXXXXXX[default]
aws_secret_access_key=XXXXXX and changing it to the below fixed it [default]
aws_access_key_id=XXXXXXXX
aws_secret_access_key=XXXXXX |
@liamroth - Thanks for the update. The change you made is correct and our documentation goes into more detail and has some examples. Related Links: |
It was happening because you did not setup the default user
@jamesls 's answer worked for me try if you are using aws2 then make sure you use |
I found that aws cli was failing due to not being able to reach the link-local
|
seems like leftovers from aws#891
I can successfully use the awscli when specifying the environment variables:
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
, however in previous installs of awscli:~/.aws/config
- which is not currently working for meAlso, specifying the
AWS_CONFIG_FILE
does not work eitherWas able to reproduce on an AWS EC2 instance and locally on Vagrant box
Failing examples:
Successful examples:
Debug flag on:
Any ideas?
I would prefer to use
AWS_CONFIG_FILE
instead of KEY and SECRETThanks, - Jesse
The text was updated successfully, but these errors were encountered: