enabling-lambda-vpc-internet-access

Provision NAT Gateway infrastructure for outbound internet access from VPC-attached Lambda functions.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill enabling-lambda-vpc-internet-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enabling-lambda-vpc-internet-access
Source: https://github.com/mreferre/aws-agent-toolkit-skills/tree/main/.kiro/skills/enabling-lambda-vpc-internet-access
Command: npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill enabling-lambda-vpc-internet-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AWS Lambda functions running inside VPC private subnets often cannot reach the public internet because they do not have public IP addresses, breaking outbound calls to external services.

Core Features & Use Cases

  • Creates NAT Gateway-based egress: Sets up NAT Gateway infrastructure to provide outbound internet access from private subnets.
  • Configures subnet routing: Updates private subnet route tables so 0.0.0.0/0 traffic flows through the NAT Gateway.
  • Validates security group egress: Ensures the Lambda security group outbound rules permit required HTTP/HTTPS traffic (typically ports 80 and 443).
  • Use Case: Enable an existing VPC-attached Lambda to call a third-party API (e.g., payment provider, ticketing system, or public URL endpoints) without moving the function out of the VPC.

Quick Start

Ask the AI to set up NAT Gateway egress for your Lambda by following the Lambda VPC internet access setup procedure for the specific lambda function name you provide.

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 enable outbound internet access for a Lambda function in a VPC private subnet?

To enable outbound internet access for a Lambda function in a VPC private subnet, provision a NAT Gateway and update the subnet route tables to direct 0.0.0.0/0 traffic through it.

Why does my VPC-attached Lambda fail to reach external API endpoints?

Your VPC-attached Lambda fails to reach external API endpoints because private subnets lack public IP addresses, requiring a NAT Gateway and proper route table configuration for egress.

What security group egress rules are required for Lambda VPC networking to access the internet?

Security group egress rules for Lambda VPC networking must allow outbound traffic on required ports, typically HTTP port 80 and HTTPS port 443, to successfully reach public internet endpoints.

Can I configure a NAT Gateway for serverless egress without moving my Lambda out of the VPC?

Yes, you can configure NAT Gateway serverless egress without moving your Lambda out of the VPC by updating private subnet routing and security group outbound rules to allow external calls.

What is the best way to route 0.0.0.0/0 traffic from VPC Lambda subnets to the public internet?

The best way to route 0.0.0.0/0 traffic from VPC Lambda subnets to the public internet is deploying a NAT Gateway and ensuring route tables direct outbound traffic through it with IGW readiness.