AWS to GCP Region Mapping — Complete Code Reference

AWS to GCP Region Code Mapping

Translating region codes between AWS and GCP is essential for multi-cloud architectures and migration planning. While AWS and GCP use similar geographic naming conventions, the specific code formats differ.

Complete Mapping Table

Location	AWS Code	GCP Code
US East (Virginia)	us-east-1	us-east1
US East (Ohio)	us-east-2	us-east4
US West (Oregon)	us-west-2	us-west1
US West (California)	us-west-1	us-west2
Canada (Montreal)	ca-central-1	northamerica-northeast1
Ireland	eu-west-1	europe-west1
Frankfurt	eu-central-1	europe-west3
London	eu-west-2	europe-west2
Paris	eu-west-3	europe-west9
Stockholm	eu-north-1	europe-north1
Tokyo	ap-northeast-1	asia-northeast1
Seoul	ap-northeast-2	asia-northeast3
Singapore	ap-southeast-1	asia-southeast1
Sydney	ap-southeast-2	australia-southeast1
Mumbai	ap-south-1	asia-south1
Sao Paulo	sa-east-1	southamerica-east1

Naming Convention Comparison

• AWS: {continent}-{direction}-{number} (e.g., us-east-1)
• GCP: {continent/country}-{direction}{number} (e.g., us-east1) — no hyphen before the number

The key difference: AWS uses hyphens before the numeric suffix (us-east-1) while GCP does not (us-east1). This small difference frequently causes configuration errors in multi-cloud setups.

Terraform Multi-Cloud Example

# AWS provider
provider "aws" {
  region = "us-east-1"
}

# GCP provider (equivalent region)
provider "google" {
  region = "us-east1"
}