I'm using the AWS CLI, an AWS SDK, or an application to access my Amazon S3 bucket, but I'm getting the error "The AWS Access Key Id you provided does not exist in our records." Why?

Resolution

The error message "The AWS Access Key Id you provided does not exist in our records" indicates that there's an issue with the credentials that you're using. The access key that you're using might have been deleted, or the associated AWS Identity and Access Management (IAM) role or user might have been deleted.

To resolve the issue, check credentials that you're using. If you're using the AWS CLI, run this command to list the stored access keys:

aws configure list

You can also run the get-caller-identity AWS CLI command to get details on the IAM credentials you're using to call the API:

aws sts get-caller-identity

Note: If you receive errors when you run AWS CLI commands, then see Troubleshoot AWS CLI errors. Also, make sure that you're using the most recent AWS CLI version.

If you're using an AWS SDK, run the GetCallerIdentity action for the SDK that you're using. 

After you obtain the credentials that you're using, verify that those credentials are still valid. If you're using an IAM role, follow these steps:

1. Open the IAM console.
2. Choose Roles.
3. Verify that the IAM role is listed. If the role isn't listed, then create a new IAM role.

If you're using an IAM user, follow these steps:

1. Open the IAM console.
2. Choose Users.
3. Verify that the IAM user is listed. If the user isn't listed, then you must create a new IAM user.
4. If the IAM user is listed, choose the user name to view its Summary page.
5. Choose the Security credentials tab, and then check whether the associated Access keys appear. If the access keys are missing or inactive, then you must create new access keys or activate the keys.

Note: If you're using a session token, make sure to pass the session token with the access key and secret key.

Related information

Configuring the AWS CLI