- Newest
- Most votes
- Most comments
Hi,
Could you double check an answer I provided a month ago to similar issue?
Otherwise, one option you can try is to remove the permissions, save the iam role, and re add them.
Hope it helps ;)
The lambda execution role is specific to the lambda function itself. I have a feeling you are getting confused between the role you are using to access AWS vs. this execution role. You shouldn't need to "configure" a VPC for Lambda, Lambda does this by itself when you place it inside a VPC and it has the correct permissions. You can find a Lambda's execution role via this screen in the console:
I am referring to the same execution role that you highlighted on the image you posted, not an IAM user. As for the VPC configuration I am referring to the VPC tab below "Permissions". As of now it is empty ('No VPC configuration This function isn't connected to a VPC.'), but I am trying to connect it to a VPC I have already created, apologies if that was a bit unclear.
If it can help narrow it down, this is a list of permissions that should be active for the execution role:
https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html
Has all the info
Relevant content
- asked 2 years ago

I actually stumbled upon your answer while I was looking for a solution, ands subsequently tried it, but it didn't solve my problem. I will give removing and re-adding the permissions a go.