Stay organized with collectionsSave and categorize content based on your preferences.
This page
applies toApigeeandApigee hybrid.
This page provides information about data residency and the locations where API hub is available.Data residencydescribes 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 providesdata residencyto 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. WhenSemantic Searchis enabled, Vertex AI is automatically provisioned within a Google Cloud region that resides within the selected multi-region.
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-poweredSemantic Searchfeature, 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 chooseUS multi-region, Vertex AI could be provisioned inus-west1,us-central1, or any other valid region within theUS multi-region.
Supported locations
The following table lists the locations where API hub is available.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-08 UTC."],[[["\u003cp\u003eThis information applies to both Apigee and Apigee hybrid, detailing the supported locations for API hub instance provisioning and Vertex AI search data.\u003c/p\u003e\n"],["\u003cp\u003eAPI hub is available in specific regions across the Americas, Europe, and Asia-Pacific, as listed in the provided tables.\u003c/p\u003e\n"],["\u003cp\u003eDuring API hub instance setup, users must specify the physical region for the API hub instance and a multi-region for Vertex AI search data if Semantic Search is enabled.\u003c/p\u003e\n"],["\u003cp\u003eWhen using Semantic Search, Vertex AI is provisioned within a Google Cloud region that falls under the user's chosen multi-region.\u003c/p\u003e\n"]]],[],null,["*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\nThis 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.\n\nAPI hub and data residency\n\n\nApigee API hub provides [data residency](/apigee/docs/api-platform/get-started/drz-concepts#data-residency-compatibility) 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.\n\n\nWhen 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](/apigee/docs/apihub/search-apis) is enabled, Vertex AI is automatically provisioned within a Google Cloud region that resides within the selected multi-region.\n\nLocation selection\n\nDuring the [API hub instance provisioning process](/apigee/docs/apihub/provision), you must specify the following locations:\n\n1. **API hub instance region:** This is the physical geographic region where your API hub instance will be hosted. **Note:** Before provisioning API hub in your project, verify if you have an existing Apigee organization in your project. If yes, then ensure the following:\n | - Ensure that [data residency (DRZ)](/apigee/docs/api-platform/get-started/drz-concepts) is not enabled for the organization.\n | - Ensure that the organization does not have the `Google Cloud Platform - Resource Location Restriction` organization policy constraint added.\n2. **Vertex AI search data multi-region:** If you enable the Vertex AI-powered [Semantic Search](/apigee/docs/apihub/search-apis) 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 in `us-west1`, `us-central1`, or any other valid region within the `US multi-region`.\n\nSupported locations\n\n\nThe following table lists the locations where API hub is available. \n\nAmericas\n\n| Region description | Region name | Details |\n|--------------------|---------------------------|----------------------------------------------------------|\n| Columbus | `us-east5` |\n| Dallas | `us-south1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Iowa | `us-central1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Las Vegas | `us-west4` |\n| Los Angeles | `us-west2` |\n| Montreal | `northamerica-northeast1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Northern Virginia | `us-east4` |\n| Oregon | `us-west1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Salt Lake City | `us-west3` |\n| Santiago | `southamerica-west1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| São Paulo | `southamerica-east1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| South Carolina | `us-east1` |\n| Toronto | `northamerica-northeast2` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n\nEurope\n\n| Region description | Region name | Details |\n|--------------------|---------------------|----------------------------------------------------------|\n| Belgium | `europe-west1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Berlin | `europe-west10` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Finland | `europe-north1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Frankfurt | `europe-west3` | |\n| London | `europe-west2` |\n| Madrid | `europe-southwest1` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Milan | `europe-west8` |\n| Netherlands | `europe-west4` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n| Turin | `europe-west12` |\n| Warsaw | `europe-central1` |\n| Zurich | `europe-west6` | [Low CO~2~](/sustainability/region-carbon#region-picker) |\n\nAsia-Pacific\n\n| Region description | Region name |\n|--------------------|------------------------|\n| Delhi | `asia-south2` |\n| Hong Kong | `asia-east2` |\n| Jakarta | `asia-southeast2` |\n| Melbourne | `australia-southeast2` |\n| Mumbai | `asia-south1` |\n| Osaka | `asia-northeast2` |\n| Seoul | `asia-northeast3` |\n| Singapore | `asia-southeast1` |\n| Sydney | `australia-southeast1` |\n| Taiwan | `asia-east1` |\n| Tokyo | `asia-northeast1` |\n\nMiddle East\n\n| Region description | Region name |\n|--------------------|---------------|\n| Dammam | `me-central2` |\n| Doha | `me-central1` |\n| Tel Aviv | `me-west1` |\n\nAfrica\n\n| Region description | Region name |\n|--------------------|-----------------|\n| Johannesburg | `africa-south1` |"]]
Low CO 2
