Thuta Learning
Search
BasicDevOpsbeginner

AWS Global Infrastructure

Relax. We'll talk through this in plain words — no textbook voice.

What you'll walk away with

  • Understand AWS Global Infrastructure without the intimidation
  • Be able to run the AWS CLI/Console yourself
  • Apply this concept immediately in a real project

Let's think about this for a second

A Region is a geographic area on the map (for example, us-east-1 = N. Virginia, ap-southeast-1 = Singapore) — you choose which Region to create each AWS resource in (picking a Region closer to your users means lower latency). An Availability Zone (AZ) is a cluster of data centers within a Region (isolated, with its own power/network) — every Region has at least 3 AZs — if you spread resources across 2 (or 3) AZs, your app can keep running even if one AZ goes down (high availability). Edge Locations are the many additional locations used by CloudFront (CDN) to deliver content from as close to the user as possible.

Let's connect this to a real scenario

If you want to run an app for users in Myanmar, choosing the ap-southeast-1 (Singapore) Region will likely give you the lowest latency — choosing us-east-1 (Virginia) means requests from Myanmar take longer to travel. If you put a production database in just one AZ, the whole database can become unavailable if that AZ goes down — split replicas across 2 AZs, and if one goes down the other can keep serving traffic.

Let's look at it together

text
AWS Global Infrastructure
===========================

Region: ap-southeast-1 (Singapore)
├── AZ: ap-southeast-1a
├── AZ: ap-southeast-1b
└── AZ: ap-southeast-1c

Region: us-east-1 (N. Virginia)
├── AZ: us-east-1a
├── AZ: us-east-1b
└── ... (6 AZs total)

Resources spread across 2+ AZs in the same region
survive a single AZ outage.
You should see
You'll be able to explain how Region, AZ, and Edge Location relate to each other.

5-minute try-it

Open the AWS Console (no account needed — the public documentation works too) and browse the list of Regions — try to guess which Region would give you the lowest latency from Myanmar.

A quick word of caution

Pricing and service availability can differ from Region to Region — double-check the pricing page before creating resources in a new Region.

Easy traps

  • Picking a Region at random — if it's too far from your users, latency goes up and the app slows down
  • Putting all production resources in a single AZ — if that AZ goes down, it becomes a single point of failure

Now try it yourself

Open the AWS Console (no account needed — the public documentation works too) and browse the list of Regions — try to guess which Region would give you the lowest latency from Myanmar.

You'll know it worked when: You'll be able to explain how Region, AZ, and Edge Location relate to each other.

AWS Global Infrastructure | Thuta Learning