Lambda VPC placement should match its private-resource requirements

What it checks

Lambda: configured with nonempty VPC subnets and security groups.

Where it applies

Terraform: aws_lambda_function

CloudFormation: AWS::Lambda::Function

How to fix it

1. Confirm private-resource requirements and inspect subnet routes, security groups, and measured initialization duration before changing VPC configuration. Connecting Lambda to a public subnet does not provide internet access or a public IP.

Frameworks

• AWS Well-Architected PERF.4

These mappings are advisory, not an attestation of compliance.

Vendor documentation

All rules