L1. AWS Global Infrastructure: Regions, AZs, and Edge Locations
Video generating
Check back soon for the video lesson on AWS Global Infrastructure: Regions, AZs, and Edge Locations
AWS operates one of the world's largest cloud networks. The Cloud Practitioner exam tests how Regions, Availability Zones, and Edge Locations work together and when to use each for availability and performance.
AWS Regions
An AWS Region is a geographical area containing multiple, isolated Availability Zones. Each Region is a separate geographic area. Current scale: AWS operates 30+ Regions worldwide (as of 2026), with more launching regularly. How to choose a Region:
- Compliance and data residency: some data must remain in a specific country or jurisdiction
- Latency: choose the Region closest to your end users
- Service availability: not all AWS services are available in every Region
- Pricing: prices vary by Region
Availability Zones (AZs)
An Availability Zone is one or more discrete datacenters within a Region, each with redundant power, networking, and connectivity. AZs are physically separate (often miles apart) but connected by high-speed, low-latency fiber. Key facts:
- Each Region has a minimum of 3 AZs (some have 6)
- AZs within a Region are isolated from each other's failures
- Resources deployed across multiple AZs achieve high availability
- AZ names (e.g., us-east-1a) are randomized per account to distribute load
Local Zones
AWS Local Zones place compute, storage, and database closer to large population centers, enabling single-digit millisecond latency for demanding applications. Use when: you need very low latency for interactive applications in a metro area not served by a full Region.
Wavelength Zones
AWS Wavelength embeds AWS compute and storage within telecommunications providers' 5G networks, enabling ultra-low latency for mobile edge applications.
Edge Locations and CloudFront
Edge locations are AWS Points of Presence (PoPs) distributed globally for content delivery. Amazon CloudFront (AWS's CDN) uses edge locations to cache content close to end users. Key fact: There are 400+ edge locations worldwide, far more than the number of Regions. This extends AWS's reach without full Regional infrastructure.
| Infrastructure | Count | Purpose |
|---|---|---|
| Regions | 30+ | Full AWS service deployment |
| Availability Zones | 90+ | High availability within Regions |
| Edge Locations | 400+ | CDN caching and low-latency delivery |
- ✓A Region is a geographical area with multiple isolated Availability Zones
- ✓AZs are separate datacenters within a Region with independent power and networking; 3+ per Region
- ✓Deploy across multiple AZs for high availability; single-AZ deployments have a single point of failure
- ✓Edge locations (400+) are CDN caching points for CloudFront; far more numerous than Regions
- ✓Choose a Region based on compliance, latency, service availability, and pricing
1. A company wants to minimize latency for customers in Tokyo but their workload is deployed in us-east-1. What should they use to serve static content faster?
2. What is the minimum number of Availability Zones in an AWS Region?
Recommended: Pluralsight
Complement these lessons with Pluralsight: structured CLF-C02 learning paths, AWS hands-on labs, and realistic practice questions for exam day.