View a markdown version of this page

lambda-inside-vpc - Amazon Config
Proactive EvaluationAmazon CloudFormation template
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

lambda-inside-vpc

Checks if a Lambda function is allowed access to a virtual private cloud (VPC). The rule is NON_COMPLIANT if the Lambda function is not VPC enabled.

Identifier: LAMBDA_INSIDE_VPC

Resource Types: AWS::Lambda::Function

Trigger type: Configuration changes

Amazon Web Services Region: All supported Amazon regions except China (Ningxia) Region

Parameters:

subnetIds (Optional)
Type: CSV

Comma-separated list of subnet IDs that Lambda functions must be associated with.

Proactive Evaluation

For steps on how to run this rule in proactive mode, see Evaluating Your Resources with Amazon Config Rules. For this rule to return COMPLIANT in proactive mode, the resource configuration schema for the StartResourceEvaluation API needs to include the following inputs, encoded as a string: 

"ResourceConfiguration":
...
{
   "VpcConfig": {
         "SubnetIds": "[SubnetId-1, SubnetId-2, SubnetId-3, ...]"
   }
} 
...

For more information on proactive evaluation, see Evaluation Mode.

Amazon CloudFormation template

To create Amazon Config managed rules with Amazon CloudFormation templates, see Creating Amazon Config Managed Rules With Amazon CloudFormation Templates.