Cloud architecture defines how applications and infrastructure are distributed across geographical locations, isolated zones, and interconnected networks to achieve availability, resilience, and performance goals. It operates at the physical layer (regions, availability zones, data centers) and the logical layer (failover strategies, redundancy patterns, replication models). Understanding cloud architecture is essential because a single misconfigured zone placement or missing health check can turn a minor hardware failure into a service-wide outage. The key mental model: cloud providers give you building blocks for resilience—but you must assemble them correctly, and in 2026 that means layering in Zero Trust security, observability, FinOps, and cloud-native deployment practices from day one.
What This Cheat Sheet Covers
This topic spans 15 focused tables and 118 indexed concepts, 114 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Physical Cloud Infrastructure
The literal geography of the cloud — the building blocks providers give you to place workloads in the world. Regions and Availability Zones are the everyday units of resilience, while Local Zones, Edge Locations, and Wavelength Zones push compute closer to users, and Outposts and Sovereign Regions handle the cases where data must stay on your premises or inside a legal jurisdiction.
| Component | Example | Description | |
|---|---|---|---|
us-east-1, eu-west-1 | • Separate geographic area with multiple isolated data centers • Regions are independent to limit blast radius of failures. | ||
us-east-1a, us-east-1b | • Isolated data center within a Region with separate power, network, and cooling • minimum of 3 AZs per Region (AWS standard). | ||
us-west-2-lax-1 | Low-latency extension of a Region placed closer to population centers for single-digit millisecond latency to end users. | ||
CloudFront POP in London | • Content delivery endpoint globally distributed for caching static content near users via CDN • 400+ locations worldwide (AWS). | ||
Boston Wavelength Zone (Verizon 5G) | 5G network edge infrastructure embedded in telecom provider networks for ultra-low latency mobile applications (< 10ms). | ||
AWS Outposts rack in customer data center | On-premises cloud hardware that brings AWS services to your own facility for low latency or data residency requirements. | ||
East US ↔ West US | Paired regions at least 300 miles apart within same geography for geo-redundant disaster recovery and sequential update rollouts. | ||
AWS GovCloud (US), Azure Government | Physically isolated region for government or regulated workloads — separate from commercial infrastructure with restricted access and dedicated compliance controls. | ||
United States, Europe, Asia Pacific | Data residency boundary that groups regions sharing compliance, sovereignty, and fault isolation requirements. |