aws-private-network-preflight

Blocks public Internet exposure in private AWS networking changes before apply.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill aws-private-network-preflight-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-private-network-preflight
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/aws-private-network-preflight
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill aws-private-network-preflight-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AWS work in GCC, GovTech, restricted, or private-only network lanes can accidentally introduce public Internet exposure through Internet Gateways, NAT Gateways, public IPs, or internet-facing load balancers. This Skill enforces a default-deny guardrail that stops such changes before they are applied. ## Core Features & Use Cases - Hard Block List: Refuses to create or propose Internet Gateways, NAT Gateways, public subnets, Elastic IPs, public EC2 IPs, internet-facing ALB/NLB, 0.0.0.0/0 routes to IGW/NAT, and public SSH/RDP access. - Scoped Preflight Triggers: Runs the full public-exposure preflight only when the task touches VPCs, subnets, route tables, gateways, public IPs, load balancers, Transit Gateway, VPC peering, PrivateLink, or security group exposure. - Lightweight EC2-Only Check: For EC2 launches in an already-approved private subnet, verifies only AssociatePublicIpAddress=false, the correct private subnet, and PublicIpAddress=null. - Use Case: Before applying a Terraform change that adds a new subnet and route table in a GovTech private lane, run this preflight to confirm no IGW, NAT, public IP, or internet-facing load balancer is introduced, and record the required public-exposure check line in the plan. ## Quick Start Use the aws-private-network-preflight skill to check this planned VPC and subnet change for any public Internet exposure before applying it.

Frequently Asked Questions about aws-private-network-preflight

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

FAQPage Schema
How do I prevent public Internet exposure in AWS private subnets?▼

Run a public-exposure preflight before any networking change that confirms no Internet Gateway, NAT Gateway, public subnet, public IP, Elastic IP, internet-facing load balancer, or default route to IGW/NAT exists. If any check returns yes, stop before applying the change.

When should I run a full AWS network preflight versus a lightweight EC2 check?▼

Run the full preflight when the task creates or updates VPCs, subnets, route tables, gateways, public IPs, load balancers, Transit Gateway, VPC peering, PrivateLink, or security group exposure. For EC2-only launches in an already-approved private subnet, only verify AssociatePublicIpAddress=false, the correct subnet, and PublicIpAddress=null.

What AWS resources are blocked in private-only network lanes?▼

The hard block list covers Internet Gateways, NAT Gateways, egress-only Internet Gateways, public subnets, EC2 instances with public IPs, Elastic IPs, internet-facing ALB or NLB, 0.0.0.0/0 or ::/0 routes to IGW/NAT, and public SSH or RDP access.

What private alternatives replace NAT Gateways and public access in AWS?▼

Prefer private subnets, VPC endpoints and PrivateLink, Transit Gateway, VPC peering, an approved private proxy path, and SSM Session Manager instead of public SSH. These provide connectivity without any public Internet exposure.

How do I clean up an accidental public-exposure test lane in AWS?▼

Freeze changes, capture dependency evidence, delete resources in safe dependency order, verify removal with direct AWS API calls, and save the evidence under ~/.AGENTS-temp/<repo>/. Do not continue other work until removal is verified.