AWS Lambda Create Function - Request failed with status code 403

user_1581921 0
Viewed 7126

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

aws-serverless amazon-iam aws-lambda amazon-web-services
9 Answers

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

user_11517410

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.

user_100832630

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

user_66297830

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.

user_2488230

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

user_160549340

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

user_98743920

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.

user_161879380

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

user_17867620

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.

user_175589440
Related