Core lesson 4 of 18Topic: AWS foundations
AWS Regions vs Availability Zones: placement and failure boundaries
A Region is a separate geographic area; an Availability Zone (AZ) is an isolated location within a Region. Two instances in one Region are not necessarily spread across AZs. Separate resource placement, the failure boundary and the application design needed to continue serving requests.
Explain the Region/AZ hierarchy, distinguish single-AZ, multi-AZ and multi-Region placement, and identify dependencies that placement alone does not fix.
Know the roles of a VM and stored data. Diagrams are synthetic placement examples, not observations of real outages or service health.
AZs belong to Regions; instance count is not placement
Region R
AZ 1 and AZ 2 are in the same Region. Cross-AZ placement still needs application and data design.
Region S
Separate from Region R. EC2 resources are not automatically replicated here.
If all instances occupy one location affected by a failure, all may be unavailable. Spreading instances across AZs addresses that placement risk, but placement alone does not implement traffic failover or data synchronization.
Choose a Region from requirements, not distance alone
| Area | What to check |
|---|---|
| Capabilities | Are the required services and features available? |
| Users and connectivity | Will latency and connection requirements be met? Distance alone is not a measurement. |
| Data and organizational requirements | Review location, legal/contractual needs and organizational policy. |
| Account | Check account type, Region enablement and accessible AZs. |
| Costs and dependencies | Review regional terms, transfer and dependency placement. |
When inspecting EC2 resources, establish both account and selected Region. An empty list in one Region does not establish that another Region has no resources. Keep that scope when investigating costs or cleanup.
Worked example: two app instances and one storage dependency
| Layout | Boundary separated | Still to establish |
|---|---|---|
| Two instances in AZ 1 | More than one instance | Both still share the AZ’s failure boundary |
| One instance in AZ 1 and one in AZ 2 | Instance placement spans AZs | Traffic distribution, data, capacity and shared dependencies |
| A deployment in another Region | Placement spans Regions | Replication, failover, destinations, operations and cost |
Choose an option to see the result and explanation.
Use AZ IDs when matching physical placement across accounts
Do not infer cross-account physical placement from the AZ code’s final letter alone. AWS documents independently mapped codes in certain older Regions for accounts created before November 2025; accounts created starting that month receive the same mappings.
An AZ ID identifies the same physical AZ across accounts. Check the account and Region conditions and compare AZ IDs when coordinating placement. Avoid both blanket claims: that letters always differ and that they always match.
Review placement together with dependencies and recovery
- List the account, Region, AZ and relevant resources.
- Identify resources that share a failure boundary.
- For multiple AZs, design traffic handling and data access.
- For multiple Regions, do not assume automatic resource or data replication.
- Define recovery requirements and evaluate them in an authorized environment.
Check, then explain in your own words
- Draw AZs within their Region.
- Compare two instances in one AZ with instances in separate AZs.
- Include data, traffic failover and AZ IDs in a placement review.
Check your understanding: Does creating an EC2 instance in another Region automatically copy the original data?
No. Required resources, data replication and failover need their own design.
EC2 resources are not automatically replicated across Regions. More locations and a working continuity design are distinct outcomes.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Regions and Zones — Amazon EC2Checked:
Scope and conditionsRegion/AZ isolation and placement; EC2 resources are not automatically replicated across Regions. Multi-AZ placement needs application and dependency design.
Used in this lessonAZs belong to Regions; instance count is not placement Choose a Region from requirements, not distance alone Worked example: two app instances and one storage dependency
- AWS RegionsChecked:
Scope and conditionsRegion geography, account types, available capabilities and enablement. No fixed global Region count or legal-suitability guarantee.
Used in this lessonAZs belong to Regions; instance count is not placement Choose a Region from requirements, not distance alone
- AWS Availability ZonesChecked:
Scope and conditionsAZ codes and AZ IDs. Independent mapping is conditional on older Regions and accounts created before November 2025; newer accounts use matching mappings. Available AZs can depend on account conditions.
Used in this lessonAZs belong to Regions; instance count is not placement Use AZ IDs when matching physical placement across accounts
Scope and conditionsVolumes attached to EC2 and independent point-in-time snapshots. No storage performance or recoverability guarantee for an actual workload.
Used in this lessonWorked example: two app instances and one storage dependency