Week 3: Regions, Availability Zones, and Edge Locations, Explained Simply
Three weeks into my AWS journey, and this week's topic finally explained something I'd always wondered: where does "the cloud" physically live?
The cloud has an address
Cloud isn't floating in the sky. It's real servers in real buildings. AWS organises those buildings into three layers.
1. Regions: the city
A Region is a geographic area where AWS has data centres, for example Mumbai (ap-south-1), Frankfurt, or N. Virginia. Regions are fully isolated from each other, so a problem in one doesn't affect another.
Four things decide which Region you pick:
- Compliance: do laws require your data to stay in a particular country?
- Proximity: the closer to your users, the lower the latency
- Available services: not every service launches everywhere at once
- Pricing: the same service can cost different amounts in different Regions
My simple rule: if users are in India, pick Mumbai, unless a law or a missing service says otherwise.
2. Availability Zones: the neighbourhoods
Each Region contains multiple Availability Zones (AZs). An AZ is one or more data centres, far enough apart that a flood or power cut won't take out two at once, but close enough for fast connections between them.
The analogy that worked for me: imagine storing your exam notes. One copy in your room is one AZ. If your room floods, the notes are gone. Copies in your room and at a friend's house across town is two AZs. One disaster can't destroy both.
This is why AWS recommends running applications across at least two AZs. It's also why "high availability" questions almost always point to a multi-AZ answer.
3. Edge locations: the local shops
Edge locations are smaller sites spread around the world that cache content close to users. They're used by CloudFront, AWS's content delivery network.
Say your website's images sit in Mumbai, and a user in London opens it. Without an edge location, every image travels from Mumbai, which is slow. With one, the images are cached in London, and that user plus everyone nearby gets them almost instantly.
There are far more edge locations than Regions, because their job is being near people, not running your applications.
Putting the three together
| Layer | What it is | Purpose |
|---|---|---|
| Region | A geographic area with multiple AZs | Where your app runs |
| Availability Zone | One or more data centres in a Region | Fault tolerance within a Region |
| Edge location | A caching site worldwide | Fast delivery to users |
How I'm picturing it
A Region is a city. AZs are separate neighbourhoods in that city, each with its own power and water, so one failing doesn't affect the others. Edge locations are corner shops in many cities, stocking copies of popular items so people don't travel to the warehouse.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article