We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
We've recently started using this:
https://github.com/awslabs/aws-config-rules/blob/master/aws-config-conformance-packs/Operational-Best-Practices-for-Serverless.yaml
It's really helped us improve our serverless stack, but we also have a question.
As we understand it, Lambda functions run in a VPC by default, the VPC owned by the Lambda service.
So adding Lambdas to a VPC is not a Lambda security requirement
There are only a couple reasons you'd want to add the extra complexity of running a Lambda in your own VPC:
If the above is correct, why is LambdaInsideVpc in the Operational Best Practices for Serverless ruleset?
LambdaInsideVpc
Many thanks!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
We've recently started using this:
https://github.com/awslabs/aws-config-rules/blob/master/aws-config-conformance-packs/Operational-Best-Practices-for-Serverless.yaml
It's really helped us improve our serverless stack, but we also have a question.
As we understand it, Lambda functions run in a VPC by default, the VPC owned by the Lambda service.
So adding Lambdas to a VPC is not a Lambda security requirement
There are only a couple reasons you'd want to add the extra complexity of running a Lambda in your own VPC:
If the above is correct, why is
LambdaInsideVpc
in the Operational Best Practices for Serverless ruleset?Many thanks!
The text was updated successfully, but these errors were encountered: