This page applies to Apigee and Apigee hybrid.
This page provides information about data residency and the locations where API hub is available. Data residency describes where your data is stored at rest. To help comply with data residency requirements, Google Cloud gives you the ability to control where that data is stored.
API hub and data residency
Apigee API hub provides data residency to keep your data-at-rest physically within a specified geographical region or location. This ensures that your data is stored and managed within the chosen geographical boundary, helping you meet any regulatory and compliance requirements.
When you provision an Apigee API hub instance, you must specify the location where the instance will be hosted. This location is used to store the data associated with the API hub instance. During provisioning, you can also specify the multi-region where your search data will be stored. When Semantic Search is enabled, Vertex AI is automatically provisioned within a Google Cloud region that resides within the selected multi-region.
Supported locations
The following table lists the locations where API hub is available.
Americas
| Region description | Region name | Details |
|---|---|---|
| Columbus |
us-east5
|
|
| Dallas |
us-south1
|
 Low CO2
|
| Iowa |
us-central1
|
Low CO2
|
| Las Vegas |
us-west4
|
|
| Los Angeles |
us-west2
|
|
| Montreal |
northamerica-northeast1
|
Low CO2
|
| Northern Virginia |
us-east4
|
|
| Oregon |
us-west1
|
Low CO2 |
| Salt Lake City |
us-west3
|
|
| Santiago |
southamerica-west1
|
Low CO2
|
| São Paulo |
southamerica-east1
|
Low CO2
|
| South Carolina |
us-east1
|
|
| Toronto |
northamerica-northeast2
|
Low CO2
|
Europe
| Region description | Region name | Details |
|---|---|---|
| Belgium |
europe-west1
|
Low CO2
|
| Berlin |
europe-west10
|
Low CO2
|
| Finland |
europe-north1
|
Low CO2
|
| Frankfurt |
europe-west3
|
Low CO2
|
| London |
europe-west2
|
|
| Madrid |
europe-southwest1
|
Low CO2
|
| Milan |
europe-west8
|
|
| Netherlands |
europe-west4
|
Low CO2
|
| Turin |
europe-west12
|
|
| Warsaw |
europe-central1
|
|
| Zurich |
europe-west6
|
Low CO2
|
Asia-Pacific
| Region description | Region name |
|---|---|
| Delhi |
asia-south2
|
| Hong Kong |
asia-east2
|
| Jakarta |
asia-southeast2
|
| Melbourne |
australia-southeast2
|
| Mumbai |
asia-south1
|
| Osaka |
asia-northeast2
|
| Seoul |
asia-northeast3
|
| Singapore |
asia-southeast1
|
| Sydney |
australia-southeast1
|
| Taiwan |
asia-east1
|
| Tokyo |
asia-northeast1
|
Middle East
| Region description | Region name |
|---|---|
| Dammam |
me-central2
|
| Doha | me-central1 |
| Tel Aviv |
me-west1
|
Africa
| Region description | Region name |
|---|---|
| Johannesburg |
africa-south1
|
Location selection
During the API hub instance provisioning process, you must specify the following locations:
- API hub instance region: This is the physical geographic region where your API hub instance will be hosted.
- Vertex AI search data multi-region: If you enable the Vertex AI-powered Semantic Search feature, you must also select the multi-region where your search data will be stored. When Semantic Search is enabled, Vertex AI is automatically provisioned within a Google Cloud region that resides within the selected multi-region. For example, if you choose
US multi-region, Vertex AI could be provisioned inus-west1,us-central1, or any other valid region within theUS multi-region.