creating-production-vpc-multi-az

Creates a multi-AZ AWS VPC with subnets, NAT gateways, route tables, and security groups.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill creating-production-vpc-multi-az-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-production-vpc-multi-az
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/creating-production-vpc-multi-az
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill creating-production-vpc-multi-az-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually provisioning a production-grade AWS VPC across multiple Availability Zones involves dozens of interdependent resources and error-prone CIDR planning. This Skill automates the entire workflow so the network foundation is consistent, tagged, and validated every time. ## Core Features & Use Cases - Full VPC provisioning: Creates the VPC with DNS support, internet gateway, public and private subnets across 2-6 AZs with automatic CIDR calculation. - High-availability networking: Deploys a NAT gateway per AZ, configures public and private route tables, and enables VPC Flow Logs to CloudWatch with a 90-day retention policy. - Tiered security groups: Builds web, application, database, and optional SSH security groups with controlled CIDR-based ingress and warnings for 0.0.0.0/0 rules. - Use Case: A platform engineer needs a staging environment network in eu-west-1. They provide a VPC name, region, environment tag, and allowed web CIDRs, and receive a validated multi-AZ VPC with a full infrastructure summary and cost estimates. ## Quick Start Create a production VPC named myapp-vpc in us-east-1 across 3 availability zones for the production environment, allowing web access from 203.0.113.0/24.

Frequently Asked Questions about creating-production-vpc-multi-az

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

FAQPage Schema
How do I create a multi-AZ VPC on AWS with public and private subnets?

Provide a VPC name, AWS region, environment tag, and allowed web CIDRs. The procedure creates the VPC with DNS support, calculates subnet CIDRs automatically, and provisions public and private subnets across 2 to 6 Availability Zones.

How to set up NAT gateways for private subnet internet access on AWS?

The procedure allocates an Elastic IP and creates a NAT gateway in each public subnet, then routes each private subnet's 0.0.0.0/0 traffic through its corresponding NAT gateway. It waits for gateways to become available before configuring route tables.

What parameters are required to create a production VPC with this procedure?

Required parameters are vpc_name, region, environment, and allowed_web_cidrs. Optional parameters include vpc_cidr (default 10.0.0.0/16), availability_zones (default 3, range 2-6), enable_ssh_access, and ssh_allowed_cidrs.

Does the VPC setup allow 0.0.0.0/0 for web access security groups?

Yes, but only if explicitly requested. The procedure warns that 0.0.0.0/0 opens web access to the entire internet and recommends specific CIDR ranges for production workloads before proceeding.

Why does NAT gateway creation take several minutes during VPC setup?

AWS NAT gateways take several minutes to reach the available state after creation. The procedure explicitly waits for availability before configuring private route tables, so this delay is expected behavior.

What happens if my AWS region has fewer than 2 Availability Zones?

The procedure validates the region with aws ec2 describe-availability-zones and stops if fewer than 2 AZs are available, since multi-AZ high availability requires at least two zones.