How nagarajurahul/terraform-aws-multi-az-vpc works
Main components
• VPC – The central boundary for all network resources.
• Public Subnets – Deployed across multiple AZs and hosting the Internet Gateway (and possibly the NAT Gateway).
• Private Subnets – Also spread across multiple AZs, which route outbound traffic via the NAT Gateway.
• Internet Gateway – Attached to the VPC to provide internet access for the public subnets.
• NAT Gateway (optional) – Used to route traffic from private subnets to the internet.
• Route Tables – Configured in the VPC for managing routing between subnets, to the Internet Gateway, and optionally the NAT Gateway.
• IPv6 Block – Show as an attribute or additional layer for the VPC and its subnets when IPv6 support is enabled.
Relationships and interactions
• The VPC encloses all components.
• Public subnets are connected directly to the Internet Gateway, allowing for direct internet access.
• Private subnets do not have a direct route to the Internet Gateway; instead, they funnel traffic through the NAT Gateway.
• Route Tables are applied to both public and private subnets and dictate routing paths.
• In an environment with IPv6 enabled, emphasize that both the VPC and subnets are assigned IPv6 CIDR blocks.
• Multi-AZ nature by drawing separate public and private subnets for each Availability Zone (AZ), highlighting the high-availability design.
Architectural patterns and design principles
• Separation of concerns: Clear distinction between public and private network areas.
• Scalability and future-proofing with IPv6 integration.
Incorporate relevant technologies
• Terraform – as the IAC tool used to manage the deployment.
• AWS – components like VPC, subnets, Internet Gateway, NAT Gateway, and Route Tables.
• (Optionally) AWS DNS support for naming.