The AWS Access Key Id does not exist in our records

Question

I created a new Access Key and configured that in the AWS CLI with aws configure  It created the  ini file in    aws config  When I run aws s3 ls it gives      A client error  InvalidAccessKeyId  occurred when calling the ListBuckets operation  The AWS Access Key Id you provided does not exist in our records    AmazonS3FullAccess policy is also attached to the user  How to fix this

User · Answer

Adding one more answer since all the above cases didn't work for me.

In AWS console, check your credentials(My Security Credentials) and see if you have entered the right credentials.

Thanks to this discussion: https://forums.aws.amazon.com/message.jspa?messageID=771815

User · Answer

Maybe you need to active you api keys in the web console  I just saw that mine were inactive for some reason

User · Answer

you can configure profiles in the bash profile file using   lt profile name gt  aws access key id    lt access key gt  aws secret access key    lt acces key secret gt    if you are using multiple profiles  then use   aws s3 ls --profile  lt profile name gt

User · Answer

Besides aws access key id and aws secret access key  I also added aws session token in  credentials  it works for me

User · Answer

For me  I was relying on IAM EC2 roles to give access to our machines to specific resources   I didn t even know there was a credentials file at    aws credentials  until I rotated removed some of our accessKeys at the IAM console to tighten our security  and that suddenly made one of the scripts stop working on a single machine   Deleting that credentials file fixed it for me

User · Answer

Assuming you already checked Access Key ID and Secret    you might want to check file team-provider-info json which can be found under amplify  folder  quot awscloudformation quot            quot AuthRoleName quot    quot  lt role identifier gt  quot          quot UnauthRoleArn quot    quot arn aws iam   lt specific to your account and role gt  quot          quot AuthRoleArn quot    quot arn aws iam   lt specific to your account and role gt  quot          quot Region quot    quot us-east-1 quot          quot DeploymentBucketName quot    quot  lt role identifier gt  quot          quot UnauthRoleName quot    quot  lt role identifier gt  quot          quot StackName quot    quot amplify-test-dev quot          quot StackId quot    quot arn aws cloudformation  lt stack identifier gt  quot          quot AmplifyAppId quot    quot  lt id gt  quot         IAM role being referred here should be active in IAM console

User · Answer

If you get this error in an Amplify project  check that  quot awsConfigFilePath quot  is not configured in amplify  config local-aws-info json In my case I had to remove it  so my environment looked like the following           INCORRECT        This will not use your profile in    aws credentials  but instead the      specified config file path       quot dev quot            quot configLevel quot    quot project quot          quot useProfile quot   false         quot awsConfigFilePath quot    quot  Users dev1  amplify awscloudformation cEclTB7ddy quot                 CORRECT      quot dev quot          quot configLevel quot    quot project quot        quot useProfile quot   true       quot profileName quot    quot default quot

User · Answer

another thing that can cause this  even if everything is set up correctly  is running the command from a Makefile  for example  I had a rule   awssetup          aws configure         aws s3 sync s3   mybucket whatever     when I ran make awssetup I got the error  fatal error  An error occurred  InvalidAccessKeyId  when calling the ListObjects operation  The AWS Access Key Id you provided does not exist in our records   but running it from the command line worked

User · Answer

I tries below steps and it worked  1  cd   2  cd  aws 3  vi credentials 4  delete  aws access key id    aws secret access key    by placing cursor on that line and pressing dd  vi command to delete line    Delete both the line and check gain

User · Answer

It looks like some values have been already set for the environment variables AWS ACCESS KEY ID and AWS SECRET ACCESS KEY   If it is like that  you could see some values when executing the below commands   echo  AWS SECRET ACCESS KEY echo  AWS ACCESS KEY ID   You need to reset these variables  if you are using aws configure  To reset  execute below commands   unset AWS ACCESS KEY ID unset AWS SECRET ACCESS KEY

User · Answer

If you have an AWS Educate account and you get this problem      An error occurred  InvalidAccessKeyId  when calling the ListBuckets operation  The AWS Access Key Id you provided does not exist in our records      The solution is here    Go to your C   drive and search for  aws folder inside your main folder in windows  Inside that folder you get the  credentials  file and open it with notepad  Paste the whole key credential from AWS account to the same notepad and save it  Now you are ready to use you AWS Educate account

User · Answer

This could happen because there s an issue with your AWS Secret Access Key  After messing around with AWS Amplify  I ran into this issue  The quickest way is to create a new pair of AWS Access Key ID and AWS Secret Access Key and run aws configure again  I works for me  I hope this helps

User · Answer

To those of you who run aws s3 ls and getting this exception  Make sure You have permissions to all regions under the provided AWS Account  When running aws s3 ls you try to pull all the s3 buckets under the AWS Account  therefore  in case you don t have permissions to all regions  you ll get this exception - An error occurred  InvalidAccessKeyId  when calling the ListBuckets operation  The AWS Access Key Id you provided does not exist in our records  Follow Describing your Regions using the AWS CLI for more info

User · Answer

Looks like    aws credentials was not created  Try creating it manually with this content    default  aws access key id   sdfesdwedwedwrdf aws secret access key   wedfwedwerf3erfweaefdaefafefqaewfqewfqw    on my test box  if I run aws command without having credentials file  the error is Unable to locate credentials  You can configure credentials by running  aws configure    Can you try running these two commands from the same shell you are trying to run aws     export AWS ACCESS KEY ID AKIAIOSFODNN7EXAMPLE   export AWS SECRET ACCESS KEY wJalrXUtnFEMI K7MDENG bPxRfiCYEXAMPLEKEY   and then try aws command

User · Answer

None of the up-voted answers work for me  Finally I pass the credentials inside the python script  using the client API   import boto3 client   boto3 client   s3   aws access key id ACCESS KEY  aws secret access key SECRET KEY  aws session token SESSION TOKEN    Please notice that the aws session token argument is optional  Not recommended for public work  but make life easier for simple trial

User · Answer

I had the same problem in windows and using the module aws-sdk of javascript  I have changed my IAM credentials and the problem persisted even if i give the new credentials through the method update like this s3 config update       accessKeyId   ACCESS KEY ID       secretAccessKey   SECRET ACCESS KEY       region   REGION         After a while i found that the module aws-sdk had created a file inside the folder User on windows with this path  C  Users User  aws credentials    The credentials inside this file take precedence over the other data passed through the method update  The solution for me was to write here  C  Users User  aws credentials  the new credentials and not with the method s3 config update

User · Answer

I made the mistake of setting my variables with quotation marks like this  AWS ACCESS KEY ID  quot     quot

User · Answer

You may have configured AWS credentials correctly  but using these credentials  you may be connecting to some specific S3 endpoint  as was the case with me   Instead of using  aws s3 ls  try using  aws --endpoint-url https    lt your s3 endpoint url gt  s3 ls  Hope this helps those facing the similar problem

User · Answer

You may need to set the AWS DEFAULT REGION environment variable

User · Answer

It might be happening that you have the old keys exported via env variables  bash profile  and since the env variables have higher precedence over credential files it is giving the error  the access key id does not exists    Remove the old keys from the bash profile and you would be good to go   Happened with me once earlier when I forgot I have credentials in bash profile and gave me headache for quite some time

[amazon-web-services] The AWS Access Key Id does not exist in our records

Examples related to amazon-web-services

Examples related to amazon-s3

Examples related to aws-cli