enabling-lambda-vpc-internet-access

Configures NAT Gateway infrastructure to give VPC-deployed Lambda functions outbound internet access.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill enabling-lambda-vpc-internet-access-richardnroman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: enabling-lambda-vpc-internet-access
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/enabling-lambda-vpc-internet-access
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill enabling-lambda-vpc-internet-access-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AWS Lambda functions attached to VPC subnets cannot receive public IP addresses, so they cannot reach the internet by default. This Skill diagnoses the VPC network setup and provisions the NAT Gateway, routing, and security group changes needed to restore outbound connectivity. ## Core Features & Use Cases - VPC Network Analysis: Inspects the Lambda function's subnets, route tables, Internet Gateways, and existing NAT Gateways using AWS CLI before making changes. - NAT Gateway Provisioning: Creates Internet Gateways, public subnets, Elastic IPs, and NAT Gateways, then updates private route tables with a 0.0.0.0/0 route. - Cost-Safe Approval Gate: Presents all billable resources and estimated costs for explicit user confirmation before creating anything. - Use Case: A Lambda function in a private subnet times out calling an external API. Use this Skill to analyze the VPC, create the NAT Gateway infrastructure, update route tables and security groups, and restore internet access. ## Quick Start Enable internet access for my Lambda function named payment-processor that is deployed in a VPC and currently cannot reach external APIs.

Frequently Asked Questions about enabling-lambda-vpc-internet-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give a Lambda function in a VPC internet access?▼

Lambda functions in VPC subnets cannot receive public IPs, so you must create a NAT Gateway in a public subnet and add a 0.0.0.0/0 route from the Lambda subnet's route table to that NAT Gateway. Security group egress rules must also allow the required ports.

Why does my VPC Lambda function timeout when calling external APIs?▼

Timeouts usually occur because the private subnet's route table lacks a 0.0.0.0/0 route to a NAT Gateway, or security group outbound rules block ports 80 and 443. Verify both the route table association and egress rules.

What AWS resources are created to enable Lambda internet access?▼

The setup creates an Internet Gateway (if missing), a public subnet with its own route table, an Elastic IP, a NAT Gateway, and a private route table with a NAT route. NAT Gateways and Elastic IPs incur ongoing charges, so approval is required first.

How long do VPC network changes take to take effect?▼

VPC networking changes such as NAT Gateway creation and route table updates can take 1-2 minutes to propagate through AWS infrastructure. Wait before testing Lambda connectivity after making changes.

What alternatives exist to NAT Gateway for Lambda internet access?▼

If the Lambda function only needs to reach specific AWS services, VPC endpoints are a cheaper alternative that avoids NAT Gateway costs. The procedure suggests VPC endpoints when the user declines NAT Gateway creation.