Bucket locations

This page explains the concept of bucket location and the different locations where you can create buckets. A bucket's location defines the physical place where object data in the bucket resides.

To learn how to set the location for your bucket, see Create buckets.

Key concepts

  • You permanently set a geographic location for storing your object data when you create a bucket.

  • You can select from the following location types:

    • A region is a specific geographic place, such as São Paulo.

    • A dual-region is a specific pair of regions, such as Tokyo and Osaka.

    • A multi-region is a large geographic area, such as the United States, that contains two or more geographic places.

  • The location type determines how your data is replicated and priced.

  • Cloud Storage stores object data in the selected location in accordance with the Service Specific Terms.

  • The location information for a bucket is part of the bucket's metadata, which you can view if you have permission to do so.

Location considerations

When you choose the location for a Cloud Storage bucket, consider the differences in availability, price, and performance, as shown in the following table.

Region Dual-region Multi-region
Availability
  • Data redundancy across availability zones (synchronous)
  • RTO(recovery time objective)=0: automated failover and failback on zonal failure (no need to change storage paths)
  • Higher availability than regions for a given storage class
  • Data redundancy across regions (asynchronous)
  • Turbo replication option for replication within 15 minutes
  • RTO(recovery time objective)=0: automated failover and failback on regional failure (no need to change storage paths)
  • Higher availability than regions for a given storage class
  • Data redundancy across regions (asynchronous)
  • RTO(recovery time objective)=0: automated failover and failback on regional failure (no need to change storage paths)
Performance
  • 200 Gbps (per region, per project)
  • Scalable to many Tbps by requesting higher bandwidth quota
  • 200 Gbps (per region, per project)
  • Scalable to many Tbps by requesting higher bandwidth quota
  • 50 Gbps (per region, per project)
  • Limited performance scaling, variable performance for reads
Pricing
  • Lowest storage price
  • No replication charges
  • No outbound data transfer charges when reading data inside the same region
  • Highest storage price
  • Replication charges apply on write
  • No outbound data transfer charges when reading data within either region
  • Higher storage price than regions, but lower than dual-regions
  • Replication charges apply on write
  • Outbound data transfer charges always apply when reading data

Location recommendations

Requirements Recommended bucket location Workload examples
  • Optimized latency and bandwidth
  • Lowest data storage cost
  • Cross-zone redundancy
Region
  • Analytics
  • Backup and archive
  • Optimized latency and bandwidth
  • Cross-region redundancy
Dual-region1
  • Analytics
  • Backup and archive
  • Disaster recovery
  • Cross-geography data access
  • Cross-region redundancy
Multi-region
  • Content serving
  1. If you need a short and predictable recovery point objective (RPO), enable the premium turbo replication feature.
  • To maximize performance and lower your total cost of ownership, co-locate your data and compute in the same region(s). Regions and dual-regions are both suitable for this purpose.
  • To avoid data replication charges, store short-lived datasets in regions.
  • For moderate performance and ad hoc analytics workloads, multi-region storage can be a cost-effective choice.

  • See the data storage pricing table for storage costs in each location.

Compute Engine VM notes

  • Storing data in the same region as your Compute Engine VM instances can provide better performance. This advantage applies to both regions and dual-regions.
  • While you can't specify a Compute Engine zone as a bucket location, all Compute Engine VM instances in zones within a given region have similar performance when accessing buckets in that region.

Available locations

The following sections list the Cloud Storage locations available for storing your data.

Regions

Geographic Area Region Name Region Description
North America
NORTHAMERICA-NORTHEAST1 Montréal leaf icon Low CO2
NORTHAMERICA-NORTHEAST2 Toronto leaf icon Low CO2
US-CENTRAL1 Iowa leaf icon Low CO2
US-EAST1 South Carolina
US-EAST4 Northern Virginia
US-EAST5 Columbus
US-SOUTH1 Dallas
US-WEST1 Oregon leaf icon Low CO2
US-WEST2 Los Angeles
US-WEST3 Salt Lake City
US-WEST4 Las Vegas
South America
SOUTHAMERICA-EAST1 São Paulo leaf icon Low CO2
SOUTHAMERICA-WEST1 Santiago leaf icon Low CO2
Europe
EUROPE-CENTRAL2 Warsaw
EUROPE-NORTH1 Finland leaf icon Low CO2
EUROPE-SOUTHWEST1 Madrid
EUROPE-WEST1 Belgium leaf icon Low CO2
EUROPE-WEST2 London leaf icon Low CO2
EUROPE-WEST3 Frankfurt leaf icon Low CO2
EUROPE-WEST4 Netherlands
EUROPE-WEST6 Zürich leaf icon Low CO2
EUROPE-WEST8 Milan
EUROPE-WEST9 Paris leaf icon Low CO2
EUROPE-WEST10 Berlin
EUROPE-WEST12 Turin
Asia
ASIA-EAST1 Taiwan
ASIA-EAST2 Hong Kong
ASIA-NORTHEAST1 Tokyo
ASIA-NORTHEAST2 Osaka
ASIA-NORTHEAST3 Seoul
ASIA-SOUTHEAST1 Singapore
India
ASIA-SOUTH1 Mumbai
ASIA-SOUTH2 Delhi
Indonesia
ASIA-SOUTHEAST2 Jakarta
Middle East
ME-CENTRAL1 Doha
ME-CENTRAL2 Dammam, Saudi Arabia
ME-WEST1 Tel Aviv
Australia
AUSTRALIA-SOUTHEAST1 Sydney
AUSTRALIA-SOUTHEAST2 Melbourne
Africa
AFRICA-SOUTH1 Johannesburg

Dual-regions

When creating a dual-region bucket, the pair of regions that you use to make the dual-region must be within the same multi-region. You include the code for that multi-region in the LOCATION parameter when creating your bucket, and that multi-region code is also specified when using customer-managed encryption keys or the resource locations constraint with a your dual-region.

The following regions are currently supported for creating dual-regions:

Multi-region code Region Name Region Description
ASIA
ASIA-EAST1 Taiwan
ASIA-NORTHEAST11 Tokyo
ASIA-NORTHEAST21 Osaka
ASIA-SOUTHEAST1 Singapore
AU
AUSTRALIA-SOUTHEAST1 Sydney
AUSTRALIA-SOUTHEAST2 Melbourne
CA
NORTHAMERICA-NORTHEAST1 Montréal
NORTHAMERICA-NORTHEAST2 Toronto
EU
EUROPE-CENTRAL2 Warsaw
EUROPE-NORTH12 Finland
EUROPE-SOUTHWEST1 Madrid
EUROPE-WEST1 Belgium
EUROPE-WEST3 Frankfurt
EUROPE-WEST42 Netherlands
EUROPE-WEST8 Milan
EUROPE-WEST9 Paris
IN
ASIA-SOUTH1 Mumbai
ASIA-SOUTH2 Delhi
US
US-CENTRAL13 Iowa
US-EAST1 3 South Carolina
US-EAST4 Northern Virginia
US-EAST54 Columbus
US-SOUTH1 Dallas
US-WEST1 Oregon
US-WEST2 Los Angeles
US-WEST3 Salt Lake City
US-WEST4 Las Vegas

1ASIA-NORTHEAST1 and ASIA-NORTHEAST2 must currently be paired together, and this dual region pairing behaves differently than typical dual-region pairings. For more information, see predefined dual-regions.

2The EUROPE-NORTH1 and EUROPE-WEST4 dual-region pairing behaves differently than typical dual-region pairings. For more information, see predefined dual-regions.

3The US-CENTRAL1 and US-EAST1 dual-region pairing behaves differently than typical dual-region pairings. For more information, see predefined dual-regions.

4US-EAST5 must currently be paired with either US-CENTRAL1 or US-EAST1.

Predefined dual-regions

The following dual-region pairings exist only as predefined dual-regions, which differ in some ways from most dual-region pairings:

Predefined dual-region name Region Description
ASIA1 Tokyo + Osaka
EUR4 Finland + Netherlands
NAM4 Iowa + South Carolina

Keep in mind the following when using predefined dual-regions:

  • Predefined dual-regions generally cannot be created using a typical dual-region creation workflow. They must be created without a custom placement configuration and with their predefined dual-region name set as the location. Once created, such buckets display the predefined dual-region name as the location and do not contain a custom placement configuration.

    • Some tools hide some or all of this behavior for predefined dual-regions. For example, in the Google Cloud console, bucket creation is the same for all dual-region pairs. However, once created, the Google Cloud console displays the location of predefined dual-regions using their predefined name, and such buckets are subject to the rest of the considerations listed in this section.
  • Predefined dual-regions require different Cloud KMS keys compared to other dual-regions in the same continent. For more information, see Customer-managed encryption key restrictions.

  • Predefined dual-regions bill storage usage against their locational SKUs, whereas typical dual-regions bill against their underlying regions.

  • When using the resource locations constraint in an organization policy, predefined dual-regions are not included with the multi-region in which they reside, whereas typical dual-regions are. Predefined dual-regions must either be explicitly added when setting the constraint, or be part of a value group that's included in the constraint.

Multi-regions

Multi-Region Name Multi-Region Description
ASIA Data centers in Asia, excluding Hong Kong and Indonesia
EU Data centers within member states of the European Union*
US Data centers in the United States

* Object data added to a bucket in the EU multi-region is not stored in the EUROPE-WEST2 (London) or EUROPE-WEST6 (Zurich) regions.

What's next

Try it for yourself

If you're new to Google Cloud, create an account to evaluate how Cloud Storage performs in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

Try Cloud Storage free