Generated banner for Creating Production Vpc Multi Az
Generated logo for Creating Production Vpc Multi Az

Creating Production Vpc Multi Az

AWSOfficialPublished by AWS

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • No issues found

From the author

Creates a production-ready VPC with public and private subnets across multiple Availability Zones, including internet gateway, NAT gateways, route tables, and security groups following AWS Well-Architected principles. Use when deploying multi-AZ VPC infrastructure with automatic CIDR planning and DNS resolution.
— the description by AWS

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a standardized workflow for provisioning a production-grade VPC on AWS. It automates the creation of essential networking components, including public and private subnets across multiple Availability Zones, internet gateways, NAT gateways, and security groups. The process adheres to AWS Well-Architected principles, ensuring DNS support is enabled and CIDR blocks are managed effectively. It includes validation steps to ensure regional availability and provides guidance on secure access configurations.

What it does

  • Validates AWS region availability and retrieves zone information.
  • Creates and configures a VPC with DNS hostnames and resolution enabled.
  • Provisions an Internet Gateway and attaches it to the VPC.
  • Sets up NAT Gateways for high-availability outbound traffic.
  • Configures route tables for public and private subnet traffic flow.
  • Applies tiered security groups with configurable access controls.

When to use it

  • When you need to deploy a new, production-ready VPC from scratch.
  • When you require a multi-AZ network architecture for high availability.
  • When you need to ensure your VPC follows AWS Well-Architected networking standards.
  • When you need automated CIDR planning and consistent resource tagging.

Advantages

  • Ensures consistent, repeatable infrastructure deployment.
  • Reduces manual configuration errors in complex networking setups.
  • Promotes high availability by distributing subnets across multiple zones.
  • Enforces security best practices through tiered security group management.

Usage examples

“Create a production VPC named my-app-vpc in us-east-1 with 3 AZs.”
The agent will validate the region, create the VPC, enable DNS, and provision the required subnets, gateways, and security groups across 3 AZs.
“Set up a new VPC for staging with SSH access enabled.”
The agent will execute the workflow with the 'staging' environment tag and configure the security groups to allow SSH access based on the provided CIDR.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/aws/creating-production-vpc-multi-az/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip creating-production-vpc-multi-az.zip -d .agents/skills

Documentation by AWS

Creating a Production-Ready VPC Across Multiple Availability Zones

Overview

Domain expertise for creating production-ready VPC infrastructure distributed across multiple Availability Zones. Covers VPC creation with DNS support, public and private subnet layout with automatic CIDR calculation, internet gateway, NAT gateways for high-availability outbound access, route table configuration, and tiered security groups following AWS Well-Architected principles.

Create a production VPC

To create a fully configured multi-AZ VPC with public/private subnets, NAT gateways, route tables, and security groups, follow the procedure exactly. See Production VPC creation procedure.

Key parameters:

  • vpc_name (required): Name prefix for all resources

  • region (required): Target AWS region

  • allowed_web_cidrs (required): CIDR blocks allowed for web access — allow 0.0.0.0/0 only if explicitly requested

  • vpc_cidr (optional, default 10.0.0.0/16): VPC CIDR block

  • availability_zones (optional, default 3): Number of AZs (2–6)

  • environment (required): Environment tag

  • enable_ssh_access (optional, default false): Whether to create SSH security group

Troubleshooting

Insufficient Availability Zones

The target region must have at least 2 available AZs. Use aws ec2 describe-availability-zones to verify.

NAT Gateway creation delays

NAT Gateways can take several minutes to become available. The procedure waits for availability before configuring route tables.

Security group CIDR warnings

The procedure warns about 0.0.0.0/0 for web access CIDRs and recommends specific IP ranges for production workloads, but allows it if explicitly requested.

Files

SKILL.md

Creating a Production-Ready VPC Across Multiple Availability Zones

Overview

Domain expertise for creating production-ready VPC infrastructure distributed across multiple Availability Zones. Covers VPC creation with DNS support, public and private subnet layout with automatic CIDR calculation, internet gateway, NAT gateways for high-availability outbound access, route table configuration, and tiered security groups following AWS Well-Architected principles.

Create a production VPC

To create a fully configured multi-AZ VPC with public/private subnets, NAT gateways, route tables, and security groups, follow the procedure exactly. See Production VPC creation procedure.

Key parameters:

  • vpc_name (required): Name prefix for all resources

  • region (required): Target AWS region

  • allowed_web_cidrs (required): CIDR blocks allowed for web access — allow 0.0.0.0/0 only if explicitly requested

  • vpc_cidr (optional, default 10.0.0.0/16): VPC CIDR block

  • availability_zones (optional, default 3): Number of AZs (2–6)

  • environment (required): Environment tag

  • enable_ssh_access (optional, default false): Whether to create SSH security group

Troubleshooting

Insufficient Availability Zones

The target region must have at least 2 available AZs. Use aws ec2 describe-availability-zones to verify.

NAT Gateway creation delays

NAT Gateways can take several minutes to become available. The procedure waits for availability before configuring route tables.

Security group CIDR warnings

The procedure warns about 0.0.0.0/0 for web access CIDRs and recommends specific IP ranges for production workloads, but allows it if explicitly requested.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
AWS
Publisher
AWS (Official)
Source
aws/agent-toolkit-for-aws · skills/specialized-skills/networking-and-content-delivery-skills/creating-production-vpc-multi-az · commit 0a218f8
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by AWS.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download creating-production-vpc-multi-az.zip