Non-Default VPC Access

When deploying a lambda with VPC access, everything works as expected when using the default VPC. However, if you specify a subnet and/or security group that exists in the non-default VPC, there’s no way to specify the VPC ID. Instead it just throws an error Error occurred while DescribeSecurityGroups. EC2 Error Code: InvalidGroup.NotFound. EC2 Error Message: The security group 'sg-xxxxxxxx' does not exist.

Is there a way to specify a non-default VPC ID? Is there another explanation for this error, as the AWS docs imply that the VPC ID should be inferred from the security group/subnet specification assuming they’re both part of the same VPC.

1 Like

Hey there, lukiffer!

Did you have any luck with this? I’m having the same problem…