Firestore in Datastore mode Locations

Before you use Firestore in Datastore mode, you must choose a ___location where the project's data is stored. To reduce latency and increase availability, store your data close to the users and services that need it.

Types of locations

You can store your Datastore mode data in either a multi-region ___location or a regional ___location.

Data in a multi-region ___location operates in a multi-zone and multi-region replicated configuration. Select a multi-region ___location if you want to maximize the availability and durability of your database. Multi-region locations can withstand the loss of an entire region and maintain availability without data loss. In the Datastore Service Level Agreement, multi-region locations define a higher monthly uptime percentage than regional locations.

Data in a regional ___location operates in a multi-zone replicated configuration. Select a regional ___location if your application is more sensitive to write latency or if you want co-___location with other Google Cloud resources that your application may use.

Multi-region locations

A multi-region ___location consists of a defined set of regions where multiple replicas of the database are stored. Each replica is either a read-write replica which contains all of the data in the database or a witness replica which does not maintain a full set of data but participates in replication.

By replicating the data between multiple regions, data can continue to be served even with the loss of an entire region. Within a region, data is replicated across zones so that data can continue to be served within that region even with the loss of a zone.

The following multi-region locations are available:

Multi-Region Name	Multi-Region Description	Read-Write Regions	Witness Region
`eur3`	Europe	`europe-west1` (Belgium), `europe-west4` (Netherlands)	`europe-north1` (Finland)
`nam5`	United States (Central)	`us-central1` (Iowa), `us-central2` (Oklahoma—private Google Cloud region)	`us-east1` (South Carolina)
`nam7`	United States (Central and East)	`us-central1` (Iowa), `us-east4` (Northern Virginia)	`us-central2` (Oklahoma—private Google Cloud region)

Regional ___location

A regional ___location is a specific geographic place, such as South Carolina. The following regional locations are available:

	Region Name	Region Description
North America
	`us-west1`	Oregon	Low CO₂
	`us-west2`	Los Angeles
	`us-west3`	Salt Lake City
	`us-west4`	Las Vegas
	`us-central1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Iowa	Low CO₂
	`northamerica-northeast1`	Montréal	Low CO₂
	`northamerica-northeast2` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Toronto	Low CO₂
	`northamerica-south1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Queretaro
	`us-east1`	South Carolina
	`us-east4`	Northern Virginia
	`us-east5` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Columbus
	`us-south1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Dallas	Low CO₂
South America
	`southamerica-west1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Santiago	Low CO₂
	`southamerica-east1`	São Paulo	Low CO₂
Europe
	`europe-west2`	London	Low CO₂
	`europe-west1`	Belgium	Low CO₂
	`europe-west4` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Netherlands	Low CO₂
	`europe-west3`	Frankfurt
	`europe-west8` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Milan
	`europe-southwest1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Madrid	Low CO₂
	`europe-west9` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Paris	Low CO₂
	`europe-west12` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Turin
	`europe-west10` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Berlin	Low CO₂
	`europe-north1`	Finland	Low CO₂
	`europe-north2` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Stockholm	Low CO₂
	`europe-central2`	Warsaw
	`europe-west6`	Zürich	Low CO₂
Middle East
	`me-central1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Doha
	`me-central2` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Dammam
	`me-west1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Tel Aviv
Asia
	`asia-south1`	Mumbai
	`asia-south2` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Delhi
	`asia-southeast1`	Singapore
	`asia-southeast2`	Jakarta
	`asia-east2`	Hong Kong
	`asia-east1`	Taiwan
	`asia-northeast1`	Tokyo
	`asia-northeast2`	Osaka
	`asia-northeast3`	Seoul
Australia
	`australia-southeast1`	Sydney
	`australia-southeast2` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Melbourne
Africa
	`africa-south1` This ___location does not support App Engine. If you plan to use App Engine, you should choose a different ___location.	Johannesburg

Selecting a ___location

The ___location setting for your Google Cloud project applies to both Firestore in Datastore mode and App Engine. When you select a ___location in either product, you set the ___location for your entire Google Cloud project.

If you have not yet selected a ___location for your project, you will be asked to select the ___location when you complete any of the following tasks:

Creating a new App Engine application.
Creating your first Datastore mode entity using the Google Cloud console.

Viewing the ___location of your project

Use one of the following methods to find out which ___location you selected for your project:

Run the gcloud app describe command.
If you have at least one version of an App Engine app deployed, open the App Engine Dashboard in the Google Cloud console. The ___location information in the upper right-hand corner of the dashboard applies to both App Engine and Firestore in Datastore mode.

Next steps

For more information about building applications to meet your latency, availability and durability requirements, see Geography and Regions.
For a map of locations, see Cloud Data Center Locations.