Secret Manager locations

Secret Manager resources can be created in one of many locations. For more information about locations within Google Cloud, see Geography and regions.

Secret Manager does not support zones, dual-regional locations, or multi-regional locations.

How locations work in Secret Manager

Secrets and secret versions can be accessed globally across Google Cloud. A secret's replication policy determines where the secret and its versions are stored in Google Cloud.

Secrets that use the automatic replication policy are replicated without restriction. Automatic replication is recommended for most users.

If you need more control over the locations where a secret is stored, you can choose the user-managed replication policy. With user-managed replication, you select one or more geographic locations where the secret will be replicated. For specific instructions, see Creating secrets.

For more information about availability of Secret Manager resources, refer to the service-level agreement SLA.

Regional endpoints for Secret Manager

If your data is subject to data residency zone (DRZ) regulations or other compliance requirements, create and store your Secret Manager resources in a Google Cloud location that supports regional endpoints. Regional endpoints are request endpoints that only allow requests to proceed if the affected resource exists in the location specified by the endpoint. For example, when you use the endpoint https://secretmanager.me-central2.rep.googleapis.com in a delete secret request, the request only proceeds if the secret is located in ME-CENTRAL2. Regional endpoints ensure that your data at rest and in transit remains in a specific Google Cloud location. For information about creating regional secrets, see Create regional secrets.

To identify the locations that have dedicated regional endpoints for Secret Manager, see the Regional endpoint availability column in the following tables.

Locations in Asia Pacific

The following table lists the locations in Asia Pacific where Secret Manager resources can be stored.

Location description Location name Regional endpoint availability
Delhi asia-south2 No
Hong Kong asia-east2 No
Jakarta asia-southeast2 No
Melbourne australia-southeast2 No
Mumbai asia-south1 No
Osaka asia-northeast2 No
Seoul asia-northeast3 No
Singapore asia-southeast1 No
Sydney australia-southeast1 No
Taiwan asia-east1 No
Tokyo asia-northeast1 No

Locations in Europe

The following table lists the locations in Europe where Secret Manager resources can be stored.

Location description Location name Regional endpoint availability
Belgium europe-west1 No
Berlin europe-west10 No
Finland europe-north1 No
Frankfurt europe-west3 Yes
London europe-west2 No
Milan europe-west8 Yes
Netherlands europe-west4 No
Turin europe-west12 No
Paris europe-west9 Yes
Warsaw europe-central2 No
Zurich europe-west6 Yes

Locations in North America

The following table lists the locations in North America where Secret Manager resources can be stored.

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

Locations in South America

The following table lists the locations in South America where Secret Manager resources can be stored.

Location description Location name Regional endpoint availability
São Paulo southamerica-east1 No
Santiago southamerica-west1 No

Locations in Middle East

The following table lists the locations in the Middle East where Secret Manager resources can be stored.

Location description Location name Regional endpoint availability
Dammam me-central2 Yes
Doha me-central1 No
Tel Aviv me-west1 Yes

Locations in Africa

The following table lists the locations in Africa where Secret Manager resources can be stored.

Location description Location name Regional endpoint availability
Johannesburg africa-south1 No

What's next