AWS Global Infrastructure

AWS Global Infrastructure is the physical backbone that makes Amazon Web Services work. It is a worldwide network of data centers, connection points, and edge locations that AWS operates to deliver its services reliably and with low latency to users anywhere in the world.

Understanding global infrastructure is critical because it directly impacts where applications are deployed, how fast they respond to users, and how resilient they are during failures.

Key Components of AWS Global Infrastructure

AWS global infrastructure has four main building blocks: Regions, Availability Zones, Edge Locations, and Local Zones.

1. AWS Regions

A Region is a geographic area in the world where AWS has built multiple data centers. Each Region is completely independent of other Regions. As of today, AWS has 33+ Regions globally, with more launching regularly.

Examples of AWS Regions:

us-east-1 — Northern Virginia, USA
ap-south-1 — Mumbai, India
eu-west-1 — Ireland, Europe
ap-southeast-1 — Singapore

Each Region has a unique code name. When deploying an application, a Region is selected based on where the users live, compliance requirements, and cost.

How to Choose the Right Region?

User proximity: Choose a Region closest to most users for faster response times.
Data compliance: Some countries require data to stay within their borders. For example, European companies often must use eu-west Regions due to GDPR.
Service availability: Not all AWS services are available in all Regions. Newer services often launch in us-east-1 first.
Cost: Pricing varies by Region. us-east-1 is typically the cheapest.

2. Availability Zones (AZs)

Each Region contains multiple Availability Zones. An Availability Zone is one or more physical data centers within a Region. They are connected to each other through private, high-speed fiber cables.

AZs are physically separate — different buildings, different power sources, different cooling systems, and different network connections. If one AZ goes down due to a power failure or flood, the others keep running.

REGION: ap-south-1 (Mumbai)
+----------------------------------------------+
|                                              |
|  +----------+  +----------+  +----------+   |
|  |  AZ: a   |  |  AZ: b   |  |  AZ: c   |   |
|  | Data     |  | Data     |  | Data     |   |
|  | Center 1 |  | Center 2 |  | Center 3 |   |
|  +----------+  +----------+  +----------+   |
|                                              |
|  [Connected by private high-speed fiber]     |
+----------------------------------------------+

A Region typically has 3 to 6 Availability Zones. By deploying applications across multiple AZs, high availability is achieved. This means even if one data center has an outage, the application continues running from another AZ.

3. Edge Locations

Edge Locations are small AWS data points placed in major cities around the world — separate from Regions and AZs. They are used specifically by Amazon CloudFront (AWS's content delivery network) and Route 53 (DNS service).

When a user requests a webpage or video, the content is served from the nearest Edge Location — not from the main Region. This dramatically reduces loading time.

AWS has 400+ Edge Locations globally, making CloudFront one of the fastest content delivery networks in the world.

User in Chennai, India
        |
        v
[Edge Location: Chennai] ← Content served from here (fast)
        |
        v
[Origin: EC2 in ap-south-1 Mumbai] ← Original content stored here

4. Local Zones

Local Zones are extensions of an AWS Region placed in densely populated areas. They bring AWS compute and storage services physically closer to users in cities that are far from the nearest full Region.

Example: A Local Zone in Dallas, Texas provides low-latency access for users in that area without needing to go all the way to the us-east-1 Region in Virginia.

Local Zones are ideal for applications that need single-digit millisecond latency — like live video editing, gaming, or real-time financial systems.

AWS Regions vs Availability Zones vs Edge Locations

Concept	What It Is	Count (approx.)	Main Purpose
Region	Geographic area with multiple data centers	33+	Deploy applications near users
Availability Zone	Isolated data center(s) within a Region	100+	High availability and fault tolerance
Edge Location	Content delivery point in major cities	400+	Fast content delivery via CloudFront
Local Zone	Region extension in a specific city	30+	Ultra-low latency for specific cities

Real-World Example — Streaming App

Consider a video streaming service that uses AWS:

The main application runs on EC2 servers in the ap-south-1 Region (Mumbai).
Servers are spread across 3 Availability Zones — so if one data center has a power failure, users still stream without interruption.
Video content is cached at Edge Locations in Chennai, Bengaluru, Hyderabad, and Delhi — so users get fast load times regardless of their city.

            [Mumbai Region — ap-south-1]
           /           |             \
    [AZ: a]       [AZ: b]        [AZ: c]
  App Servers   App Servers    App Servers
                      |
         [CloudFront Distribution]
        /       |        |       \
[Edge:      [Edge:   [Edge:   [Edge:
 Chennai]   Delhi]  Kolkata]  Pune]
    |           |       |        |
  Users       Users   Users    Users

High Availability vs Fault Tolerance

High Availability

High availability means the application stays running even when one part fails. Spreading servers across multiple AZs achieves this. If AZ-a goes down, AZ-b and AZ-c keep serving traffic.

Fault Tolerance

Fault tolerance goes further — the system continues without any degradation in performance, even during a failure. This requires more redundancy and is costlier but critical for banking, healthcare, and e-commerce platforms.