EC2 permissions for VPC not set on first deploy

Problem

Hi Guys, I have multiple serverless projects up and running, but today I wanted to set up a new one, and I can't figured it out. My project is inside a VPC, and I have a permission error on the "AWS::Lambda::Function" role: > Your access has been denied by EC2, please make sure your function execution role have permission to CreateNetworkInterface. EC2 Error Code: UnauthorizedOperation. EC2 Error Message: You are not authorized to perform this operation. But my serverless.yml is setup the same way than my working projects: [code block] As you can see, I clearly set the iamRoleStatements for EC2. Moreover, I read this in the documentation: > Further, if you have specified VPC security groups and subnets for your lambdas to use then the EC2 rights necessary to attach to the VPC via an ENI will be added into the default IAM policy. But when the role is created, the inline policy attached is the following: [code block] No rights about EC2 are added... Does anyone have an idea? Many thanks