AWS Config Adds Support for AWS Lambda
You can now record configuration changes to AWS Lambda using AWS Config. AWS Lambda lets you run code without provisioning or managing servers. With Config, you can track changes to the Lambda function, runtime environments, tags, handler name, code size, memory allocation, timeout settings, and concurrency settings. You can also record changes to Lambda IAM execution role, subnet, and security group associations. In addition, you can now use a managed Config rule to check whether your Lambda functions prohibit public access.
You can now record configuration changes to AWS Lambda using AWS Config. AWS Lambda lets you run code without provisioning or managing servers. With Config, you can track changes to the Lambda function, runtime environments, tags, handler name, code size, memory allocation, timeout settings, and concurrency settings. You can also record changes to Lambda IAM execution role, subnet, and security group associations. In addition, you can now use a managed Config rule to check whether your Lambda functions prohibit public access.
Support for tracking AWS Lambda functions is available in all AWS public regions where AWS Config is offered and in the AWS GovCloud (US) region. To see the full list of supported regions, visit AWS Regions and Endpoints in the AWS General Reference.
For more information on AWS Config see: