“The AWS Access Key Id Does Not Exist In Our Records” is one of the problems which might happen sometimes. Thus, we will propose some solutions below to assist you in solving this issue. 

When will the error “The AWS Access Key Id Does Not Exist In Our Records”?

This error will happen when the access key Id configured for the AWS CLI is not valid. In other words, you can face this error message when handling various AWS-named profiles for a wide range of purposes. 

This error will display on your screen during calling the ListBuckets operation.

Here is the root cause: 

The access key which you try to use can be deleted, or the associated AWS Identity and Access Management role could be deleted. 

How to fix this problem?

Approach 1: Verify ‘AWS_ACCESS_KEY_ID’ and ‘AWS_SECRET_ACCESS_KEY’

You need to verify that ‘AWS_ACCESS_KEY_ID’ and ‘AWS_SECRET_ACCESS_KEY’ environment variables are set. 

echo $AWS_ACCESS_KEY_ID
echo $AWS_SECRET_ACCESS_KEY

 Unset them like below. 

unset AWS_ACCESS_KEY_ID
unset AWS_SECRET_ACCESS_KEY

Then, reset them. 

export AWS_ACCESS_KEY_ID="<SOME_ACCESS_KEY_ID>"
export AWS_SECRET_ACCESS_KEY="<SOME_SECRET_ACCESS_KEY>"

The AWS_DEFAULT_REGION env variable is assigned by the correct value. 

Lastly, run the code, and this error is tackled completely.

Approach 2: Validate the AWS CLI configuration variables’ values

Firstly, validate the value of AWS CLI configuration variables in case you do not use env vars. 

cat ~/.aws/credentials

At this time, the credentials file might be like the one below. 

[default]
aws_access_key_id = SOME_ACCESS_KEY_ID
aws_secret_access_key = SOME_SECRET_ACCESS_KEY

If your AWS CLI configuration variables are old, please configure them again. 

AWS configure

Until the moment, this error has been removed totally from your project. 

Approach 3: Keep in mind the session token variable if you work with temp credentials

You need to remember the session token var.

~/.aws/credentials:

aws_session_token = SOME_AWS_SESSION_TOKEN

As for the environment variable, you use this syntax below. 

export AWS_SESSION_TOKEN=<SOME_AWS_SESSION_TOKEN>

Now, you solved this error completely.

Conclusion

Controlling and switching from various AWS accounts can be the main issue daily. Leave your feedback on the error: “The AWS Access Key Id Does Not Exist In Our Records”  below if you enjoy this post.   

Read more: 

→ Resolve The Error “Error installing provider “aws”: openpgp: signature made by unknown entity”