Dataproc Metastore regions

When you create a Dataproc Metastore service, you permanently set a geographic location for your service to reside in, otherwise known as a region.

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

Supported Dataproc Metastore features

The following table lists the Dataproc Metastore features.

Feature Supported
Administrator Interface
Artifacts Cloud Storage bucket
Auxiliary versions
Backup/Restore
CMEK config
Database type Spanner/MySQL
Data Catalog sync
Endpoint protocol (Thrift/gRPC)
IAM policies on
individual tables/databases
Import/Export
Kerberos
Private Service Connect
Release channels
Scaling config
VPC-SC

Single region services

Dataproc Metastore is available in the following regions. For more information about regions and zones, see Geography and regions.

Asia Pacific

Region description Region name
Taiwan asia-east1
Hong Kong asia-east2
Tokyo asia-northeast1
Seoul asia-northeast3
Mumbai asia-south1
Delhi asia-south2
Singapore asia-southeast1
Jakarta asia-southeast2
Sydney australia-southeast1
Melbourne australia-southeast2

Europe

Region description Region name
Warsaw europe-central2
Finland europe-north1
Madrid europe-southwest1
Belgium europe-west1
London europe-west2
Frankfurt europe-west3
Netherlands europe-west4
Zürich europe-west6
Milan europe-west8
Paris europe-west9
Turin europe-west12

Middle East

Region description Region name
Tel Aviv me-west1
Dammam me-central2

Dataproc Metastore services created in me-central2 can't be attached to Managed Service for Apache Spark clusters.

North America

Region description Region name
Montréal northamerica-northeast1
Toronto northamerica-northeast2
Mexico northamerica-south1
Iowa us-central1
South Carolina us-east1
Northern Virginia us-east4
Columbus us-east5
Dallas us-south1
Oregon us-west1
Los Angeles us-west2
Salt Lake City us-west3
Las Vegas us-west4

South America

Region description Region name
São Paulo southamerica-east1
Santiago southamerica-west1

What's next