Hi I m trying to understand why `securityGroupIds` is a requ

Question

Hi I m trying to understand why `securityGroupIds` is a required field in the `vpcConfig`<https www pulumi com registry packages aws api docs lambda function functionvpcconfig| for AWS Lambdas> In my architecture I have a lambda defined in the private subnet of a VPC and already attached a security group to the VPC So when I m associating the lambda with the subnet using `subnetIds` in `vpcConfig` why do I necessarily have to respecify the securityGroupId too

fresh-spring-82225 · Answer

I was wondering about that too I think the answer is that even though the security group belongs to the VPC it has to be explicitly associated with a resource lambda or EC2 instance to take effect

fresh-spring-82225 · Answer

The terminology vpc config for lambdas comes from aws but it s a little confusing because it implies that it just describes the vpc It both identifies the subnets and the security groups to use Different lambdas in the same subnet can use different security groups

few-analyst-47494 · Answer

That makes sense A VPC can have different security groups and a lambda in that VPC can have any one of those associated security groups I wonder what would happen if a security group that is not associated with a VPC is associated with a lambda in that VPC

polite-napkin-90098 · Answer

I think you d get an error telling you that the sg was not in the right VPC I ve not played with lamdbas but have seen a similar error with other resources i e ECS Fargate tasks