[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-31。"],[],[],null,["# Bucket locations\n\nThis page explains the concept of *bucket location* and the different\nlocations where you can create buckets. A bucket's location defines the\nphysical place where object data in the bucket resides.\n\nTo learn how to set the location for your bucket, see [Create buckets](/storage/docs/creating-buckets).\n\nKey concepts\n------------\n\n- You set a [geographic location](#available-locations) for storing your\n [object data](/storage/docs/objects) when you create a bucket.\n\n - You can [relocate a bucket](/storage/docs/bucket-relocation/overview) after it's created or [move your data to a bucket in a different location](/storage/docs/moving-buckets). Note that bucket relocation is available only if you've configured [Storage Intelligence](/storage/docs/storage-intelligence/overview).\n- You can select from the following location types:\n\n - A *region* is a specific geographic place, such as São Paulo.\n\n - A *dual-region* is a specific pair of regions, such as Tokyo and\n Osaka.\n\n - Dual-region pairings can be [*predefined* or *configurable*](#location-dr).\n - A *multi-region* is a large geographic area, such as the\n United States, that contains two or more geographic places.\n\n- The location type determines how your data is [replicated](/storage/docs/availability-durability#replication) and [priced](/storage/pricing#storage-pricing).\n\n- Cloud Storage stores object data in the selected location in\n accordance with the [Service Specific Terms](/terms/service-terms).\n\n- The location information for a bucket is part of the bucket's [metadata](/storage/docs/bucket-metadata),\n which you can [view](/storage/docs/getting-bucket-metadata) if you have [permission](/storage/docs/access-control/iam) to do so.\n\nLocation considerations\n-----------------------\n\nWhen you choose the location for a Cloud Storage bucket, consider the\ndifferences in availability, and price, as shown in the following\ntable.\n\n### Location recommendations\n\n1. For more information about region-specific considerations, see [Geography and regions](/docs/geography-and-regions#regions_and_zones).\n2. If you need a short and predictable [recovery point objective (RPO)](/architecture/dr-scenarios-planning-guide#basics_of_dr_planning), enable the premium [turbo replication](/storage/docs/availability-durability#turbo-replication) feature.\n\n- 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.\n- To avoid data replication charges, store short-lived datasets in regions.\n- For moderate performance and ad hoc analytics workloads, multi-region storage\n can be a cost-effective choice.\n\n- See the [data storage pricing table](/storage/pricing#storage-pricing) for storage costs in each location.\n\n### Compute Engine VM notes\n\n- Storing data in the same region as your [Compute Engine VM instances](/compute/docs/instances) can provide better performance. This advantage applies to both regions and dual-regions.\n- 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.\n\nAvailable locations\n-------------------\n\nThe following sections list the Cloud Storage locations available for\nstoring your data.\n\n### Regions\n\n^1^Montréal, Osaka, and Querétaro each have three zones housed in one\nor two physical data centers. In the rare event of a disaster, data stored in\nthese regions can be lost. To avoid this, you might want to consider using a\n[dual-region](#location-dr) or backing up business-critical data to a\nsecond region using [Storage Transfer Service](/storage-transfer-service?e=48754805) for increased data protection.\n\n### Dual-regions\n\nObjects stored in dual-region buckets are replicated so that they are stored in\neach region that make up the dual-region. The time it takes an object to be\nreplicated between the two regions is determined by the bucket's\n[replication setting](/storage/docs/availability-durability#cross-region-redundancy).\n\nThere are two types of dual-regions supported in Cloud Storage.\n\n- A *predefined dual-region* is identified by a unique location code and\n represents two specific regions. For example, `NAM4` is the location code for\n the predefined dual-region consisting of `US-CENTRAL1` and `US-EAST1`.\n\n- A *configurable dual-region* is identified by the location code of the\n geographical area in which the dual-region resides and a placement\n configuration in which you specify a pair of regions. For example, you could\n create a configurable dual-region that has a location code of `EU` and\n a placement configuration consisting of `EU-CENTRAL2` and `EU-WEST1`.\n\nIf the regions you want to pair are not available as a dual-region, consider\ncreating a separate bucket in each region and using Storage Transfer Service\n[Event-driven transfers](/storage-transfer/docs/event-driven-transfers) to keep the buckets in sync.\n\n#### Configurable dual-regions\n\nWhen [creating a bucket](/storage/docs/creating-buckets) in a configurable dual-region, the pair of regions\nthat you use to make the dual-region must use the same location code. This code\nis set for the `LOCATION` of the bucket and is also the location you specify\nwhen using [customer-managed encryption keys](/storage/docs/encryption/customer-managed-keys#restrictions) or the\n[resource locations constraint](/resource-manager/docs/organization-policy/defining-locations) with such dual-region buckets.\n| **Note:** Unlike buckets in other locations, which bill [storage usage](/storage/pricing#storage-pricing) against the SKUs associated with their location code, buckets in configurable dual-regions bill storage usage against SKUs in both of their underlying regions.\n\nThe following regions are available when creating a configurable dual-region\nbucket:\n\n^1^The `EUROPE-NORTH1` and `EUROPE-WEST4` dual-region pairing is only\navailable as a [predefined dual-region](#predefined).\n\n^2^The `US-CENTRAL1` and `US-EAST1` dual-region pairing is only\navailable as a [predefined dual-region](#predefined).\n\n^3^`US-EAST5` must be paired with either `US-CENTRAL1` or `US-EAST1`.\n\n^4^ When pairing `EUROPE-WEST8` and `EUROPE-WEST12`,\nuse the `IT` multi-region code.\n\n^5^ When pairing `EUROPE-WEST3` and `EUROPE-WEST10`, use the `DE`\nmulti-region code.\n\nAttempting to create a bucket using an invalid pairing, such as regions with\ndifferent location codes, returns an error.\n\n#### Predefined dual-regions\n\nWhen [creating a bucket](/storage/docs/creating-buckets) in a predefined dual-region, you use a\nlocation code that uniquely identifies the pair of regions, in the same way you\ncreate buckets in regions and multi-regions. This location code is what you\nspecify when using [customer-managed encryption keys](/storage/docs/encryption/customer-managed-keys#restrictions) or the\n[resource locations constraint](/resource-manager/docs/organization-policy/defining-locations) with such dual-region buckets.\n| **Note:** Some tools present all dual-regions as if they were configurable dual-regions during bucket creation. For example, when creating a bucket in a dual-region using the Google Cloud console, you always select the individual regions that are part of the dual-region. If a predefined dual-region exists for that pair, that predefined dual-region is used. Otherwise, a configurable dual-region is created. Once created, the Google Cloud console displays the correct location for that bucket, making it clear if a predefined dual-region was created.\n\nThe following options are available when creating a bucket in a predefined\ndual-region:\n\n### Multi-regions\n\n^\\*^ Object data added to a bucket in the `EU` multi-region is not\nstored in the `EUROPE-WEST2` (London) or `EUROPE-WEST6` (Zürich) regions.\n\nWhat's next\n-----------\n\n- [Create a bucket](/storage/docs/creating-buckets).\n- Get the location for an existing bucket by [viewing the bucket's metadata](/storage/docs/getting-bucket-metadata).\n- Learn more about [availability and durability in Cloud Storage](/storage/docs/availability-durability).\n- View all the [Google Cloud services available in locations worldwide](/about/locations).\n- [Explore additional location-based concepts](/docs/geography-and-regions), such as zones, that apply to other Google Cloud services.\n\nTry it for yourself\n-------------------\n\n\nIf you're new to Google Cloud, create an account to evaluate how\nCloud Storage performs in real-world\nscenarios. New customers also get $300 in free credits to run, test, and\ndeploy workloads.\n[Try Cloud Storage free](https://console.cloud.google.com/freetrial)"]]
二氧化碳排放量低