Enabling Lambda Vpc Internet Access

If your VPC Lambda can't reach the internet, this walks you through the NAT Gateway setup you need. It covers creating the NAT infrastructure, splitting public and private subnets, configuring route tables with the 0.0.0.0/0 routes, and fixing security groups. The troubleshooting section is helpful for the usual gotchas like route table associations and the 1-2 minute propagation delay that catches everyone. This is pretty focused on one specific problem, which is good because VPC networking has enough moving parts that having the exact procedure referenced beats trying to remember whether the route goes in the public or private subnet route table.

skills.sh installs: 6.5K
GitHub stars: 3.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aws/agent-toolkit-for-aws --skill enabling-lambda-vpc-internet-access --agent claude-code

Installs into .claude/skills of the current project.

Files

Enabling Lambda VPC Internet Access

Overview

Domain expertise for enabling internet access from AWS Lambda functions running inside VPC private subnets. Lambda functions in a VPC cannot receive public IP addresses, so outbound internet access requires NAT Gateway infrastructure that routes traffic from private subnets through a public subnet to an Internet Gateway.

Enable internet access for a VPC Lambda function

To set up NAT Gateway infrastructure and configure routing for a Lambda function that needs internet access, follow the procedure exactly. See Lambda VPC internet access setup procedure.