# Serverless » The provided access key is not authorized for this operation. - Please contact support and provide this identifier to reference this issue - DXLNV333D9CC **URL:** \ **Category:** Serverless Framework\ **Tags:** aws, lambda, iam\ **Created:** [October 13, 2021, 4:29pm UTC](https://forum.serverless.com/t/serverless-the-provided-access-key-is-not-authorized-for-this-operation-please-contact-support-and-provide-this-identifier-to-reference-this-issue-dxlnv333d9cc/16082 "2021-10-13T16:29:31Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![teatime](https://avatars.discourse-cdn.com/v4/letter/t/f19dbf/32.png) [@teatime](https://forum.serverless.com/u/teatime)\ **Post date:** [October 13, 2021, 4:29pm UTC](https://forum.serverless.com/t/serverless-the-provided-access-key-is-not-authorized-for-this-operation-please-contact-support-and-provide-this-identifier-to-reference-this-issue-dxlnv333d9cc/16082/1 "2021-10-13T16:29:31Z")
Hello, I’m trying to create an application using Serverless, AWS Lambda and MongoDB so I was referencing this blog post: > **[Free Tier Serverless MongoDB with AWS Lambda and MongoDB Atlas](https://mattwelke.com/2019/02/18/free-tier-serverless-mongodb-with-aws-lambda-and-mongodb-atlas.html)** > > Connect AWS Lambda to MongoDB Atlas to build a free tier MongoDB NoSQL serverless app. - I’ve created an AWS account and set up an IAM user which I’ve placed under a group with AdministratorAccess privileges and got the IAM user’s AWS Access Key and AWS Secret Access Key. - I’ve added the access keys to the environment variables (I’m using Windows 10) - I’ve installed Serverless using npm install -g serverless - Then I’ve created a template using serverless create --template aws-nodejs --path my-lambda-app - When I’m trying to run the “serverless deploy” command I receive the following error message: Serverless » The provided access key is not authorized for this operation. - Please contact support and provide this identifier to reference this issue - DXLNV333D9CC Any help would be appreciated! ---
**Author:** ![ursula](https://avatars.discourse-cdn.com/v4/letter/u/7bcc69/32.png) [@ursula](https://forum.serverless.com/u/ursula)\ **Post date:** [October 15, 2021, 8:36am UTC](https://forum.serverless.com/t/serverless-the-provided-access-key-is-not-authorized-for-this-operation-please-contact-support-and-provide-this-identifier-to-reference-this-issue-dxlnv333d9cc/16082/2 "2021-10-15T08:36:49Z")
How did you add your access key to the environement? I did this: run: `serverless config credentials` : with parameters: `--provider aws` `--key` _``_ `--secret` _``_ it saves them to: `~/.aws/credentials` ---
**Author:** ![Daniel-Andarge](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/daniel-andarge/32/7313_2.png) [@Daniel-Andarge](https://forum.serverless.com/u/Daniel-Andarge)\ **Post date:** [February 10, 2023, 9:31am UTC](https://forum.serverless.com/t/serverless-the-provided-access-key-is-not-authorized-for-this-operation-please-contact-support-and-provide-this-identifier-to-reference-this-issue-dxlnv333d9cc/16082/3 "2023-02-10T09:31:35Z")
@teatime did u fix this error i also have the issue please share the solution if u fix it ---
**Author:** ![DevJhon](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/devjhon/32/7594_2.png) [@DevJhon](https://forum.serverless.com/u/DevJhon)\ **Post date:** [August 9, 2023, 8:49pm UTC](https://forum.serverless.com/t/serverless-the-provided-access-key-is-not-authorized-for-this-operation-please-contact-support-and-provide-this-identifier-to-reference-this-issue-dxlnv333d9cc/16082/4 "2023-08-09T20:49:53Z")
Hi @Daniel-Andarge the problem is because the .aws credentials aren´t not same on the serverless/providers with the pc. ---
**Author:** ![garethmcc](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/garethmcc/32/2276_2.png) [@garethmcc](https://forum.serverless.com/u/garethmcc)\ **Post date:** [August 16, 2023, 10:28am UTC](https://forum.serverless.com/t/serverless-the-provided-access-key-is-not-authorized-for-this-operation-please-contact-support-and-provide-this-identifier-to-reference-this-issue-dxlnv333d9cc/16082/8 "2023-08-16T10:28:27Z")
The way to correct this is to delete the ~/.serverlessrc file, then run “serverless login” to rebuild it and you should be all good