Cloud Region Reference

AWS, GCP and Azure region codes with geographic locations.

Searchable reference of AWS, Google Cloud and Azure region codes mapped to their cities and geographic areas, so you can match an opaque region identifier to a real-world location. It runs free in your browser on Gera Tools, with nothing uploaded.

Last updated Source: Gera Tools

Where is AWS us-east-1?

us-east-1 is AWS's Northern Virginia region in the United States. It is the oldest and largest AWS region and the default for many global services and the AWS console, which is why it appears in so many examples and IAM/global endpoints.

Decode an opaque cloud region code

Cloud providers identify their data-centre regions with short codes that do not always reveal where they are. This reference maps the most-used AWS, Google Cloud and Azure region codes to their real cities and geographic areas, so you can tell at a glance that eu-west-2, europe-west2 and uksouth all sit in London.

How it works

Each provider follows its own naming scheme:

AWS    eu-west-2          area-direction-number   -> London, UK
GCP    europe-west2       continent-direction-num -> London, UK
Azure  uksouth            descriptive word        -> London, UK

A region groups several availability zones — physically separate data centres with independent power, cooling and networking. You spread workloads across zones within a region for resilience, and across regions for global reach or disaster recovery.

Key regions by provider

AWS

CodeLocation
us-east-1Northern Virginia (oldest, default for many global services)
us-east-2Ohio
us-west-1Northern California
us-west-2Oregon
eu-west-1Ireland
eu-west-2London
eu-central-1Frankfurt
ap-southeast-1Singapore
ap-northeast-1Tokyo

us-east-1 is special: it is the default region for AWS global services like IAM, CloudFront, and Route 53, and it tends to get new features first.

Google Cloud (GCP)

CodeLocation
us-central1Iowa
us-east1South Carolina
europe-west1Belgium
europe-west2London
europe-west3Frankfurt
asia-east1Taiwan
asia-southeast1Singapore

Azure

CodeLocation
eastusVirginia
westusCalifornia
westeuropeNetherlands
northeuropeIreland
uksouthLondon
ukwestCardiff
eastasiaHong Kong
southeastasiaSingapore

Choosing a region: the key questions

Where are your users? Latency to end-users is typically the dominant factor. A user in London making API requests to a Virginia region adds roughly 80–100 ms of round-trip time versus a London region.

Does a required service exist in that region? Newer and more specialised services sometimes roll out to major US regions first. Check the provider’s service availability matrix before committing to a region for a new project.

What are the data-residency requirements? GDPR requires personal data about EU citizens to be stored within the EU or in countries with adequate protection. UK GDPR has similar requirements. The region code tells you exactly which country the data physically lives in.

What does it cost? Compute and egress prices vary meaningfully between regions — sometimes 10–20% for the same instance type. If you are running significant workloads, compare pricing for your key services before choosing between equivalent regions.