Data Catalog resources are hosted in multiple locations worldwide, called regions. A region is a specific geographical location where you can access your resources. For more information, see Geography and Regions.
To decrease network latency, we recommend using the API endpoint for a region that is close to where you plan to use it. For example, if you plan to access Data Catalog from Asia, then you could use the endpoint for Taiwan.
Supported regions
Region | Regional endpoint | Supported resources | |
---|---|---|---|
Americas | |||
Montréal | northamerica-northeast1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Toronto | northamerica-northeast2-datacatalog.googleapis.com |
Tag templates, user created entries, Data lineage | |
São Paulo | southamerica-east1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Santiago | southamerica-west1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Iowa | us-central1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
South Carolina | us-east1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Northern Virginia | us-east4-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Columbus | us-east5-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Dallas | us-south1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Oregon | us-west1-datacatalog.googleapis.com |
Tag templates, user created entries, Data lineage | |
Los Angeles | us-west2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Salt Lake City | us-west3-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Las Vegas | us-west4-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Europe | |||
Warsaw | europe-central2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Finland | europe-north1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Belgium | europe-west1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
London | europe-west2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Frankfurt | europe-west3-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Netherlands | europe-west4-datacatalog.googleapis.com |
Tag templates, user created entries, Data lineage | |
Zurich | europe-west6-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Milan | europe-west8-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Paris | europe-west9-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Berlin | europe-west10-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Turin | europe-west12-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Madrid | europe-southwest1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Asia Pacific | |||
Taiwan | asia-east1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Hong Kong | asia-east2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Tokyo | asia-northeast1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Osaka | asia-northeast2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Seoul | asia-northeast3-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Mumbai | asia-south1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Delhi | asia-south2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Singapore | asia-southeast1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Jakarta | asia-southeast2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Sydney | australia-southeast1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Melbourne | australia-southeast2-datacatalog.googleapis.com |
Tag templates, user created entries, Data lineage | |
Middle East | |||
Doha | me-central1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Dammam | me-central2-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Tel Aviv | me-west1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage | |
Africa | |||
Johannesburg | africa-south1-datacatalog.googleapis.com |
Tag templates, BigQuery, user created entries, Data lineage |
Multi-regions (us, eu)
Multi-regions such as eu
and us
are special regions, where
Data Catalog can replicate and serve resources anywhere within
them.
Multi-region | Multi-regional endpoint | Supported resources |
---|---|---|
Asia | asia-datacatalog.googleapis.com |
Tag templates, user created entries, Data lineage |
European Union | eu-datacatalog.googleapis.com |
BigQuery, Tag templates, user created entries, Data lineage |
United States | us-datacatalog.googleapis.com |
BigQuery, Tag templates, user created entries, Data lineage |
BigQuery Omni regions
BigQuery Omni regions | Regional endpoint | Supported resources | |
---|---|---|---|
AWS | |||
AWS - US East (N. Virginia) | aws-us-east-1-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
AWS - US West (Oregon) | aws-us-west-2-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
AWS - Asia Pacific (Seoul) | aws-ap-northeast-2-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
AWS - Asia Pacific (Sydney) | aws-ap-southeast-2-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
AWS - Europe (Ireland) | aws-eu-west-1-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
AWS - Europe (Frankfurt) | aws-eu-central-1-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
Azure | |||
Azure - East US 2 (Virginia) | azure-eastus2-datacatalog.googleapis.com |
BigQuery (except connections), Data lineage | |
Azure - West US 2 (Washington) | azure-westus2-datacatalog.googleapis.com |
Data lineage |
Accessing resources with regional APIs
Resources can be accessed using regional endpoints (listed previously in Supported regions). Client libraries allow you to configure endpoints.
For backward compatibility, regional APIs are still supported by the
datacatalog.googleapis.com
endpoint, with some limitations (see
HTTP batch support and gRPC support).
It is strongly recommended that you use regional endpoints for regional APIs.
Non-regional APIs
While data assets are located in particular regions,
Data Catalog's search features are globally scoped. Non-regional
APIs like SearchCatalog
and LookupEntry
return assets from all regions,
and can be accessed with the datacatalog.googleapis.com
endpoint.
HTTP batch support
Data Catalog supports HTTP batch, letting you batch multiple API calls into a single request.
There are some constraints when using HTTP batch for regional APIs:
- A HTTP batch request must only include API requests for resources belonging to the same region.
- You must use regional endpoints when batching regional APIs.
datacatalog.googleapis.com
will not support batched regional APIs. Regional and non-regional requests cannot be batched together. - Non-region dependent APIs (SearchCatalog and LookupEntry) can be batched
together, using the
datacatalog.googleapis.com
endpoint.
If you're not sure whether whether you're using HTTP batch:
- Check whether you are directly making a HTTP request with a path set to
/batch
, such ashttp://datacatalog.googleapis.com/batch
. If you are using the Google API Client Libraries:
- Java: Using BatchRequest to call APIs.
- Python: Using BatchHTTP request to call APIs.
- Similar bindings exist for other libraries (see the library specific documentation).
gRPC support
Regional endpoints are the recommended way to use gRPC for regional APIs.
If you are using manually created gRPC libraries to make calls to the
datacatalog.googleapis.com
endpoint, you must specify a x-google-request-params
header with a locations=<region>
tag in the request. The existing
Cloud Client Libraries
that use gRPC internally already have this functionality implemented.