Regions, Availability Zones, and Edge Locations
Learn how AWS is laid out globally: Regions, AZs, Edge Locations, and how to choose where to build.
This lesson is purely conceptual — no AWS usage required.
The big picture: "AWS is not one place"
AWS is a global cloud, but it is organized into separate Regions, and inside each Region there are multiple Availability Zones.
In plain terms:
- Region = "which geographic area am I building in?"
- AZ = "which isolated location inside that Region am I building in?"
Regions
Key Terms
What a Region is
Region
A physical location in the world that contains multiple Availability Zones.
Why the Region choice matters
AWS recommends considering these factors when selecting a Region:
- Latency — pick a Region close to your users for faster response times
- Cost — pricing can vary between Regions
- Service availability — not every AWS service is available in every Region
- Compliance — some regulations require data to stay in a specific country or area
Warning
Important: Resources are NOT replicated across Regions unless you choose to do so. If you create a server in us-east-1, it does not automatically exist in eu-west-1.
Availability Zones (AZs)
Key Terms
What an AZ is
Availability Zone
One or more discrete data centers with separate and redundant power, networking, and connectivity, inside a Region.
Why AZs exist
AZs let you design systems that survive a failure of a single location in the Region by spreading components across multiple AZs.
AZ naming (prevents confusion)
AZ names look like region-code + letter (example: us-east-2a, us-east-2b).
Note
In some Regions and for some accounts, the same AZ name can map to a different physical AZ across accounts. When coordinating across accounts, use AZ IDs (the consistent physical identifiers).
Edge locations, also known as Points of Presence
Edge location
Infrastructure closer to end users that connects back to AWS Regions through AWS's backbone network.
Example: Helps deliver content faster to users far away from your Region.
Quick reference
Quick Reference
Micro-activity 1: Choose a Region like an engineer
Latency
Response time for your users
Cost
Keeping infrastructure bills down
Service availability
Access to the widest range of AWS services
Compliance
Data residency and regulatory requirements
Suggested Region
us-east-1
N. Virginia
Widest service selection — most new services launch here first
Strong global connectivity through AWS's backbone
Tradeoff: Higher traffic costs than us-west-2; more distant from non-NA users
Select an app type or user location above to get a tailored suggestion.
Think about your specific app — latency, cost, missing services, or compliance gaps.
Your answers save automatically.
Micro-activity 2: Turn "single-AZ" into "multi-AZ"
You have a simple app: a web server and a database.
Diagram A (single-AZ):
Diagram B (multi-AZ concept):
Your answers are saved automatically.
Summary
- AWS is global, but you build inside a chosen Region
- Each Region has multiple Availability Zones for fault isolation and high availability
- Many resources are not replicated across Regions unless you do it intentionally
- Edge locations help reduce latency for delivering content and edge services
- When coordinating across accounts, AZ names may differ; AZ IDs are consistent physical identifiers