Reputation: 61
previously I had been able to deploy my lambda functions without any problems on my own AWS account. Now, I need to deploy them on to a different AWS account where my IAM user has an AdministratorAccess permission.
I've set up a role/policies for invoking lambdas the same way I did for my account. Before I deployed my code with terraform, I checked the console page for AWS lambda , and this error pops up.
Any idea why I still don't have enough permissions to access lambda even with my AdministratorAccess policy attached to my user?. Do I still need to add more policies to my user in order to access Lambda?
Upvotes: 6
Views: 6168
Reputation: 367
I have faced the same issue, after checking this post I checked my mailbox. AWS asked my to verify my account by sending utility bills picture and address information. I did it and everything is back to normal now.
Upvotes: 0
Reputation: 107
I have faced the same issue. You need to contact AWS to unlock your access as your account has been locked due to potentially dangerous activity.
I recommend you to enable MFA and use an IAM user to log in to AWS console instead of root user.
Upvotes: 5
Reputation: 1722
AdministratorAccess
is definitely enough to view the Lambda console.
Do you have CLI access setup for this user? You could try running the list-functions
CLI command to confirm that you user is setup as expected, as this uses the same API call that the web console is performing for you.
Upvotes: 0