AWS Learning Journey

"Where Did My Database Go?" — AWS Regions and Availability Zones, Finally Explained

The #1 beginner AWS mistake has nothing to do with code. It's about geography.

9 min read · 1661 words
AWSCloud ComputingCloud ArchitectureDevOpsBeginners
"Where Did My Database Go?" — AWS Regions and Availability Zones, Finally Explained cover image

AWS from Zero to Production — Phase 1, Part 2 of 5 · See the full series roadmap


You create a database. You refresh the console. It’s gone.

You panic. You check the billing page. It’s still costing money — so it exists somewhere.

Then you notice the tiny dropdown in the top-right corner of the console. You switch Regions, and there it is.

Almost every AWS engineer has had this moment. And it points to something bigger: where your resources live decides how fast, how reliable, how expensive, and how legal your application is.

This article turns AWS’s global map into something you can actually reason about.

What you’ll walk away with


The physical hierarchy

AWS global network
 └── Region (e.g., eu-west-1, Ireland)
      ├── Availability Zone A ── one or more data centers
      ├── Availability Zone B ── one or more data centers
      └── Availability Zone C ── one or more data centers

Edge locations (many cities worldwide)
 └── Used by services such as CloudFront and Route 53

Regions

A Region is a separate geographic area where AWS operates infrastructure, identified by a code such as:

Regions are designed to be isolated from each other. A failure in one Region should not affect another. Your data does not leave a Region unless you, or a service you configure, move it.

AWS adds Regions regularly, so check the AWS global infrastructure page for the current list.

Opt-in Regions: Newer Regions are often disabled by default for an account and must be enabled before use. If a Region doesn’t appear in the console’s Region selector, check Account settings.

Availability Zones

An Availability Zone (AZ) is one or more discrete data centers within a Region, with independent power, cooling, and networking. AZs in a Region are physically separated — far enough to reduce the chance of a shared disaster, close enough for low-latency, high-bandwidth connections between them.

AWS designs every Region with at least three AZs. At the time of writing, AWS operates 39 Regions and 124 Availability Zones — check the AWS global infrastructure page for current numbers.

Why this matters: an AZ is your basic failure domain. If you run two copies of an application in two AZs, a power or network failure in one AZ leaves the other running. That’s the foundation of high availability on AWS.

Engineer’s note — AZ names vs. AZ IDs: An AZ name such as us-east-1a may map to a different physical zone in your account than in someone else’s. The AZ ID (for example, use1-az1) identifies the same physical zone across accounts. Use AZ IDs when coordinating resources across multiple accounts.

Edge locations

Edge locations are sites in many cities worldwide, far more numerous than Regions. They don’t host your general workloads. Instead, specific services use them to get closer to users:

We’ll use CloudFront and Route 53 in Phase 3.


Regional vs. global services

Most AWS services are regional: you choose a Region, and the resource exists only there.

The S3 special case

S3 confuses many people:

So S3 looks global but stores data regionally.

Engineer’s note: Zonal resources can’t move between AZs directly. An EBS volume in us-east-1a can only attach to an EC2 instance in us-east-1a. You’d snapshot and restore it to move it. Design around this early.


How to choose a Region

Use these four questions, in order.

1. Compliance and data residency

Are there legal or contractual requirements about where data lives? Some regulations require data to stay inside a country or economic area. This can eliminate most options immediately.

2. Latency to users

Choose a Region close to the users or systems that call your application most. For a user in Europe, a European Region will usually respond faster than one in the US.

You can do a rough check with community latency-testing tools, or by measuring from your own network.

3. Service and feature availability

Not every service, instance type, or feature launches in every Region at the same time. Check the AWS Regional services list for the services you plan to use — especially newer AI or analytics features.

4. Price

Prices for the same resource differ between Regions. Use the AWS Pricing Calculator to compare candidates once the first three questions have narrowed the list.

Engineer’s note: For a learning sandbox, pick one Region near you and stay there. Most “missing resource” confusion disappears once everything lives in one Region.


Multi-AZ vs. multi-Region

Multi-AZ

Run redundant resources across two or more AZs in one Region.

For production workloads, multi-AZ is the standard starting point.

Multi-Region

Run your workload, or a recovery copy of it, in two or more Regions.

                    Multi-AZ                  Multi-Region
Failure covered     Data center / AZ          Entire Region
Typical use         Most production systems   Strict RTO/RPO, global users
Data replication    Usually synchronous       Usually asynchronous (lag)
Operational effort  Moderate                  High

Engineer’s note: Start with multi-AZ plus backups copied to another Region. That gives strong availability and a recovery path for a fraction of the cost of active multi-Region. We’ll go deeper in Phase 10.

Service availability

Each AWS service publishes its own availability design and service-level agreement. When you design for availability, check:


Four ways to interact with AWS

1. AWS Management Console

The web interface.

2. AWS CLI

A command-line tool that calls AWS APIs.

aws s3 ls
aws ec2 describe-instances --region eu-west-1

3. AWS SDKs

Libraries for calling AWS from application code — Python (boto3), JavaScript, Java, Go, .NET, and others.

import boto3

ec2 = boto3.client("ec2", region_name="eu-west-1")
zones = ec2.describe_availability_zones()["AvailabilityZones"]

for zone in zones:
    print(zone["ZoneName"], zone["ZoneId"], zone["State"])

4. AWS CloudShell

A browser-based shell launched from the console, already authenticated as your console identity, with the AWS CLI and common tools preinstalled.

All four use the same underlying APIs and the same permissions. If you’re denied in the CLI, you’d be denied in the console too.


Common mistakes


Key takeaways


Quick self-check

Test yourself before moving on:

  1. You created an RDS database but can’t find it in the console. What’s the first thing to check?
  2. Is IAM regional or global? What about an EBS volume?
  3. Can an EBS volume in us-east-1a attach to an EC2 instance in us-east-1b?
  4. Your us-east-1a and a teammate’s us-east-1a — are they the same physical zone? How would you know for sure?

Answers

  1. The Region selector. The database almost certainly lives in another Region.
  2. IAM is global. An EBS volume is zonal — it lives in one Availability Zone.
  3. No. You’d snapshot the volume and restore it in the other AZ.
  4. Not necessarily. AZ names can map to different physical zones in different accounts. Compare AZ IDs, such as use1-az1, instead.

What’s next

In Part 3, we move from geography to governance: AWS accounts, protecting the root user, and how AWS Organizations and Control Tower help teams manage many accounts safely.

Which Region do you use most, and why? Share your reasoning in the comments.


Share this article

LinkedIn post draft