Lesson 0001: AWS Global Infrastructure

Regions, Availability Zones, Edge Locations, and High Availability

1. The Three Building Blocks

AWS runs its cloud across a globally distributed infrastructure made of three nested units. Understanding their relationships is critical for the exam because AWS asks you to choose the right configuration for latency, compliance, and resilience.

Region — A geographic area containing multiple isolated data centers. Each Region is completely independent. As of 2024, AWS has 30+ Regions worldwide. You choose a Region based on latency, cost, compliance, and service availability.
Availability Zone (AZ) — One or more discrete data centers within a Region, each with independent power, cooling, and networking. AZs are physically separated by many kilometers but connected by low-latency links. A Region has a minimum of 3 AZs (up to 6+). AZs do not share single points of failure.
Edge Location — A data center placed in major cities and metropolitan areas, closer to end users than Regions. Edge Locations run Amazon CloudFront (CDN) and AWS Global Accelerator to cache content and route traffic over the AWS backbone for lower latency.
Region (e.g., us-east-1)
  ├── AZ 1a (data center)
  ├── AZ 1b (data center)
  └── AZ 1c (data center)

Edge Locations (100+ cities)
  ├── CloudFront cache
  └── Global Accelerator endpoint

2. Why the Distinction Matters

ConcernUse ThisWhy
Protect against data center failureMultiple AZs in one RegionAZs have independent power and network. Deploying across 2+ AZs gives high availability.
Protect against regional disasterMultiple RegionsRegions are fully isolated. Use for disaster recovery, business continuity, or data sovereignty.
Reduce latency for global usersEdge Locations + CloudFrontContent is cached at the edge, closer to users, reducing round-trip time.
Meet data residency lawsA specific RegionData stored in a Region does not leave that Region unless you configure it to.
Lowest latency for mobile/IoT usersAWS Wavelength ZonesEmbed AWS compute at the edge of 5G networks. (Know the name; exam mentions it rarely.)

3. High Availability and Fault Tolerance

The exam loves to test whether you understand high availability versus fault tolerance in the context of AZs.

High Availability (HA)

Run redundant resources across multiple AZs in the same Region. If one AZ fails, traffic fails over to the other. This is the standard AWS pattern for resilience. Example: An Auto Scaling group spanning AZ 1a and AZ 1b behind an Application Load Balancer.

Fault Tolerance

A stricter form of resilience where the system continues operating without interruption during a failure. Often requires active-active multi-AZ or multi-Region setups with automated failover. The exam usually accepts multi-AZ as the answer for both HA and basic fault tolerance questions.

4. When to Use Multiple Regions

The exam will present scenarios and ask why you would deploy to more than one Region. Memorize these four reasons:

  1. Disaster recovery / business continuity — If an entire Region fails (rare but possible), a secondary Region keeps the application running.
  2. Low latency for global users — Serve users from the Region closest to them.
  3. Data sovereignty / compliance — Some laws require data to stay within a country's borders.
  4. High availability across continents — For applications that cannot tolerate even regional outages.

5. Edge Services: CloudFront and Global Accelerator

Both use Edge Locations, but they solve different problems. The exam tests whether you can distinguish them.

ServiceWhat It DoesBest For
Amazon CloudFrontContent Delivery Network (CDN). Caches static content (images, videos, HTML) at Edge Locations and serves it from the nearest edge.Web sites, streaming, software distribution — anything where you want users to download content faster.
AWS Global AcceleratorRoutes user traffic over the AWS global network to the optimal endpoint in a Region. Uses static IP addresses.Real-time applications (gaming, VoIP, financial trading) where consistent low latency matters more than caching.
Memory trick: CloudFront caches content at the edge. Global Accelerator routes traffic over the AWS backbone to your application. If the question mentions "static content" or "CDN," the answer is CloudFront. If it mentions "consistent low latency" or "static IP," the answer is Global Accelerator.

6. Quick Quiz

Test Your Understanding

Select one answer per question. You will receive immediate feedback.

1. A company wants to ensure its application remains available even if an entire data center loses power. Which approach should it use?
2. Which AWS component is specifically designed to cache content closer to end users to reduce latency?
3. A financial trading application needs the lowest possible and most consistent latency for users across three continents. Which service should it use?
4. Which statement about Availability Zones is correct?
5. A European company must store customer data within the European Union to comply with regulations. Which AWS concept helps them meet this requirement?
6. A media company wants to distribute video files to millions of users worldwide with minimal buffering. Which service should they use?
Progress: 0/6 correct (0%). Answer all questions to see the final recommendation.
Primary Source: AWS Academy Module 3: AWS Global Infrastructure Overview.
Ask your teacher: If anything in this lesson is unclear — especially the difference between CloudFront and Global Accelerator, or when multi-Region is overkill versus multi-AZ — ask me before moving to the next lesson. These distinctions appear on nearly every CLF-C02 exam.