Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

Lambda access denied

0

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?

Argomenti
ServerlessComputazionaliSicurezza, identità e conformità
Tag
AWS LambdaGestione identità e accesso AWS
Lingua
English
AWS-User-6415386
posta 2 anni fa329 visualizzazioni
1 Risposta
1

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.

AWS
Marco
con risposta 2 anni fa
  • Pronoy_C
    2 anni fa

    Also, reach out to support if it's critical.

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente