Design VPC

Plan and implement AWS VPC architectures with Terraform.

13|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill design-vpc-heaptracetechnology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Design VPC
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/cloud-engineer/vpc-design
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill design-vpc-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and implement production-grade AWS VPC architectures with proper subnet tiers, NAT gateways, security groups, NACLs, VPC peering, flow logs, and CIDR planning for multi-AZ high-availability deployments.

Core Features & Use Cases

  • CIDR planning and non-overlapping ranges across multiple VPCs and accounts
  • Three-tier subnet design (public, private, isolated) with HA NAT gateways and proper routing
  • Observability and security controls: VPC Flow Logs, Reachability checks, security groups and NACLs, VPC endpoints
  • Use Case: Deploy a multi-AZ production environment with prod-staged-dev separation and cross-VPC peering or Transit Gateway

Quick Start

Provision a production-grade VPC using Terraform to achieve multi-AZ isolation and observability.

Frequently Asked Questions about Design VPC

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

FAQPage Schema
How do I design a multi-AZ AWS VPC for high availability with Terraform?▼

Design a multi-AZ AWS VPC by provisioning three-tier subnets across availability zones, configuring HA NAT gateways, and defining routing tables with Terraform to achieve production-grade isolation and high availability.

What is the best way to plan non-overlapping CIDR ranges across multiple AWS VPCs?▼

Plan non-overlapping CIDR ranges by mapping out IP allocations across multiple VPCs and accounts before deployment, ensuring clean routing for VPC peering and avoiding conflicts during multi-region expansion.

How do I configure security groups and NACLs for a production AWS VPC?▼

Configure security groups and NACLs by applying tiered network controls across public, private, and isolated subnets, restricting traffic flow while maintaining necessary reachability for application components.

Does this VPC design support cross-account peering and Transit Gateway connectivity?▼

Yes, this VPC design supports cross-account peering and Transit Gateway connectivity, applying proper CIDR planning and routing configurations to enable secure communication across multi-account, multi-region deployments.

How do I enable VPC Flow Logs for network observability in AWS?▼

Enable VPC Flow Logs to capture network traffic metadata, providing observability across the deployment and supporting reachability checks to monitor and audit security group and NACL configurations.