Course contentsShow
← Security
Lesson 1834 of 3,05237. Cloud Security - Network ArchitectureFree lesson

Multi-AZ Subnet Design for Resilience

Distributing subnets across availability zones to ensure high availability and fault tolerance.

Multi-AZ Subnet Design for Resilience

What you'll learn: How distributing subnets across multiple availability zones creates fault-tolerant, highly available cloud network architectures.

The Core Concept

When you design a VPC, you must distribute your subnets across multiple Availability Zones (AZs) to protect against infrastructure failures. Each AZ is physically separate—think of them as isolated data centers within the same region. If one AZ experiences power failure, network issues, or natural disaster, your resources in other AZs continue operating.

Without multi-AZ design, a single infrastructure failure takes down your entire application. With proper distribution, you maintain service continuity even during zone-wide outages.

Architecture Pattern

Design subnet pairs (or groups) that mirror each other across AZs:

AZ-A:

  • Public subnet A (10.0.1.0/24) - web tier
  • Private subnet A (10.0.10.0/24) - application tier
  • Private subnet A (10.0.20.0/24) - database tier

AZ-B:

  • Public subnet B (10.0.2.0/24) - web tier
  • Private subnet B (10.0.11.0/24) - application tier
  • Private subnet B (10.0.21.0/24) - database tier

Each subnet uses its own route table and network ACL, but you configure them identically. Security groups span AZs automatically—no duplication needed.

Security Benefits

Multi-AZ design isn't just about uptime—it's a security control:

  • Blast radius containment: If an AZ is compromised, attackers cannot pivot to resources in other zones through layer-2 networking
  • Maintenance isolation: Security patching one AZ doesn't require full outages
  • DDoS resilience: Distributes attack surface across independent infrastructure
  • Backup integrity: Database replicas in separate AZs survive zone-specific disasters

Key Takeaway: Distributing identical subnets across multiple availability zones transforms single points of failure into resilient, fault-tolerant architectures while limiting the blast radius of security incidents.