By using AWS re:Post, you agree to the Terms of Use

Lambda access denied


A client has created an IAM user for me and I made sure I had all the correct permissions to finish the work. Everything was going well, I had requested a lambda concurrency limit increase (was set at 50 with an AWS default of 1000) to 500. a few days later I'm locked out of lambda even though I have lambda full access permissions set on my user. Any idea on what could be happening?

1 Answer

First, ask your client if they changed something. For example with Service Control Policies you can block Lambda Access in an Account and with that in place also with full Access on you IAM user you will not access any Lambda.
Also check if you have any DENY in you resulting policy. DENY always wins over ALLOW.

answered 9 months ago
  • Also, reach out to support if it's critical.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions