AWS Global Infrastructure and Shared Responsibility
What This Chapter Is About
Explain how AWS global infrastructure, placement choices, and the shared responsibility model fit together as one architecture decision.
Keep one durable idea in view:
Where you place the workload changes availability, latency, resilience, compliance, and operating responsibility.
Sections
How the Chapter Develops
The chapter develops in this order:
Start with the Region and Availability Zone model so the reader can reason about failure domains.
Compare Multi-AZ and Multi-Region designs so resilience trade-offs are explicit.
Add edge delivery and CDN thinking for content-heavy and globally distributed workloads.
Introduce Local Zones and Wavelength Zones as specialized placement options for latency or locality.
Apply the model to a regional design scenario with data residency and failover constraints.
Together, these sections show that infrastructure placement is an architecture choice, not a geographic afterthought.
What You Will Be Able to Do
By the end of this chapter, the reader should be able to:
Explain the relationship between AWS Regions and Availability Zones.
Describe when Multi-AZ is enough and when Multi-Region is justified.
Explain why edge delivery changes latency and traffic patterns.
Recognize when Local Zones or Wavelength Zones are better fits than a standard Region deployment.
Design a regional placement strategy that respects latency, resilience, and data residency constraints.
Key Ideas
Regions and Availability Zones define the first large fault and placement boundaries in AWS.
Multi-AZ improves resilience within a Region; Multi-Region introduces more complexity and more decisions.
Edge delivery reduces distance to users and can change how application traffic reaches the origin.
Local Zones and Wavelength Zones are specialized placement choices for latency-sensitive or locality-sensitive workloads.
Shared responsibility still applies after placement decisions are made.