Securing Lambda with VPC
Learn how to place Lambda functions within a Virtual Private Cloud (VPC) to control network access and connect to private resources.
Why Lambda in a VPC?
By default, AWS Lambda functions run within a secure, managed AWS network. However, sometimes your Lambda needs to access resources that are not publicly available, like a private database or an internal service.
This lesson explores how to place your Lambda functions inside a Virtual Private Cloud (VPC) to achieve enhanced network control and access to private resources.
What is a Virtual Private Cloud?
An AWS Virtual Private Cloud (VPC) is like your own isolated, virtual network in the AWS cloud. You define its IP address range, subnets, route tables, and network gateways.
- Subnets: Divisions within your VPC where you launch resources. They can be public (with internet access) or private (without direct internet access).
- Security Groups: Act as virtual firewalls, controlling inbound and outbound traffic for your resources.
All lessons in this course
- IAM Roles and Permissions
- API Gateway Authorizers
- Securing Lambda with VPC
- Protecting Secrets with AWS Secrets Manager