4

Trying to create a new AWS Lambda Function with the root account for the first time using management console. I am receiving the error "Request failed with status code 403" no matter how many different options I tried.

I've already tried changing my region, creating the function with default role(basic lambda permissions), new role, existing role and with the options "Author from Scratch", "Use a blueprint", "Serverless app repository" but still getting the same error.

How can i troubleshoot and solve this problem?

enter image description here

Improve this question
8
  • Have you tried changing region? Do you have permissions to create functions? Aws cli also doesn't work? Commented Nov 10, 2020 at 7:24
  • 2
    Can you check your "Personal Health Dashbord" as a suggeted here Commented Nov 11, 2020 at 0:37
  • 2
    Thanks a lot I've found the reason when i opened the dashboard. I realized that they opened a Support Case for a security leak(Risk IAM quarantine) They limited my usage of services due to this case. I've taken all the steps that they suggested and now can create a new function. Commented Nov 11, 2020 at 6:53
  • 2
    No problem. Same case for the other question. Replacing access keys helped. Commented Nov 11, 2020 at 6:55
  • 1
    @Marcin could you please write your comment as an answer? Your comment solved my problem. Commented Dec 9, 2020 at 8:48

11 Answers 11

Reset to default
1

Based on the comments.

The issue was resolved by checking Event Logs AWS Personal Health Dashboard, which indicated that permissions on the account were temporary limited by AWS due to Risk IAM quarantine and some suspicious activity.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

Faced with same issue, but "Personal Health Dashbord" is clear for me, nothing strange here.

Just about month ago i created it successfully. Also, my free tier plan was expired, but may be it the reason?

enter image description here

Also, can't delete old functions :

enter image description here

Improve this answer

2 Comments

answered to this question here : stackoverflow.com/questions/65059561/…
My problem was about a security leak. Marcin's comment solved my problem. Thanks
1

So this is essentially a role based issue and definitely seems to be a bug in the lambda console. What worked for me is to first go to the IAM console , create a role , attach a policy with 'AdministratorAccess',and in 'Trust Relationships' tab add 'lambda.amazonaws.com' as a trusted entity. After this , while creating a lambda function, use this existing role ( instead of creating a new one), and it it should work.

Improve this answer

Comments

0

Go to IAM roles. Your role already there In Lambda function configuration first try to use an existing role and chooes the role name with your function name. see if thats works.

Else since its free teir delete all IAM roles and try again

Improve this answer

Comments

0

In my case it turned out to be because my session had expired. I closed and then reopened, and the error disappeared.

Improve this answer

Comments

0

I have had similar error when tried to call the lambda from the test interface: 'An error occurred when creating the trigger: Request failed with status code 403'

the problem was that I was logged out because I was not active in the AWS console and when I re-logged then it was ok.

Improve this answer

Comments

0

Yes, it's a quarantine message by an AWS security rule or policy broke, for example: publish critical AWS data in a public repository.

Improve this answer

Comments

0

One of the problem that I saw was if you try to create behind corporate firewall, and if cdn is blocked for example below URL.. get the erro https://a.b.cdn.console.awsstatic.com/cafcd473033d51cd552a86e38ae4bbe1b0c88d6c5eab3a9b82e08864508bd0e4/hello-world-packages/nodejs16.x.zip

Improve this answer

1 Comment

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.
0

In my case, organizations security was blocking a get request of "python3.11.zip". Used dev tools to troubleshoot this.

Improve this answer

1 Comment

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.
-1

If nothing is working then just wait 24 hours and try again. It worked for me.

Improve this answer

Comments

-1

403 is access denied, and sometimes if your MFA has expired then you can refresh and try again or check for the policies if it has been changed.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.