Skip to content
All lessons
Objective 3.2Cloud Technology· 2 min read

AWS Global Infrastructure

Define the AWS global infrastructure

What you will learn

  • Order the four geographic units from smallest scope to widest spread.
  • Explain the four core factors for choosing an appropriate Region.
  • Distinguish using multiple Availability Zones for resilience within one Region from spreading across multiple Regions for different reasons.
  • Connect Edge Locations, CloudFront, and Local Zones to each one's use case.

AWS's infrastructure is organized as nested geographic layers, from the widest (Region) to the most finely spread (Edge Locations). Understanding this hierarchy prevents a common confusion between "where is my data stored" and "from where am I served the fastest response" — two entirely different questions.

The four units

RegionAn independent geographic location (like Frankfurt or Bahrain) containing several Availability Zones — the widest unit.
Availability Zone (AZ)One or more physically separate data centers within the same Region, interconnected with the other AZs by a high-speed network.
Edge LocationA small, very widely distributed site that caches content close to the user (used by CloudFront).
Local ZoneAn extension of an existing Region into a major city without a full Region, bringing limited compute resources closer to specific users.

Spreading within a Region vs. across Regions

Multiple AZs within one RegionSpreading across multiple Regions
Primary goalResilience and high availability against one data center failingGeographic proximity to users on another continent, or data residency requirements
Latency between the unitsVery low — a dedicated, high-speed networkMuch higher — real geographic distance

What matters on the exam

  • Four common Region-selection factors: latency to users, compliance and data residency requirements, whether the needed service is available there, and cost (prices vary slightly between Regions).
  • "Caching close to the user" points to Edge Locations/CloudFront, not a Region or AZ.

"The nearest Region" isn't always the right choice

A question mentioning a compliance requirement that data must stay within a specific country's borders makes that constraint win over latency alone — even if another Region is geographically closer and faster, the regulatory constraint is decided first.

Quick check

Answer in your head first, then reveal.

  1. Which of the four geographic units is the widest in scope?Reveal the answer

    Region.

  2. Which unit is used to cache content close to the user?Reveal the answer

    Edge Locations.

  3. Why might you choose a geographically farther Region despite its relative slowness?Reveal the answer

    For a compliance or data-residency requirement forcing data to stay within specific borders.

Sign in to track your progress on this topic.

Your next step

Read the lesson, then mark it complete

Sources

Used to verify the facts. The writing is original to Passuit.