InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.

Describe the bug Stretching things a bit to call this a bug, but this is where I’m at.

After I unwisely deleted the Iam User that was associated with Amplify credentials, my amplify commands stopped working. I was able to recover by running amplify configure, amplify init (existing environment: Yes), and amplify pull. Now my Amplify is associated with the new Iam User credentials, and things work as expected.

But if I go back to any previous backend configuration stored in git, my Amplify seems to get some re-association with the old credentials (although ~./aws still has the new credentials), such that any Amplify command, including amplify init and amplify pull fails with the following error:

UnhandledPromiseRejectionWarning: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records. at Request.extractError (/usr/local/nvm/versions/node/v14.9.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/services/s3.js:837:35)…

Amplify CLI Version 4.29.0

To Reproduce Described above.

Expected behavior No error.

Screenshots n/a

Desktop (please complete the following information):

• OS: Mac
• Node Version. v14.9.0

Additional context Add any other context about the problem here.

[akshbhu]

Hi @mayckonx

Can you check file local-aws-info.json present in .config folder under amplify folder and check if the profileName is same as the profile you newly created? If its different, you can do is run amplify configure project and select the correct aws-profile in the workflow.

Let me know if this works for you?

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.