Using data residency with Apigee hybrid

This topic explains how to configure a new Apigee hybrid installation for data residencycompliance.

About data residency

You can use data residency with new Apigee hybrid installations. You cannot convert an existing installation to use data residency.

Data residency meets compliance and regulatory requirements by allowing you to specify the geographic locations (regions) where Apigee data is stored. With data residency, selecting the control plane location ensures that all customer content is stored within the specified region. See also, seeIntroduction to data residency.

Basic steps for data residency configuration

To configure Apigee hybrid for data residency, you need to follow a few basic steps, including:

Creating an Apigee organization with data residency

When you create an Apigee organization, you have the option of enabling the org withdata residency. Creating an org with data residency requires you to specify twokey location attributes: thecontrol plane location and theconsumer data region.You will also need to specify thebilling type. For details, seeStep 2: Create an organization.

  • Control plane location: You need to specify the location where customer core content like proxy bundles are stored. For a list seeAvailable Apigee API control plane regions.

    The control plane location is the location of the service endpoint location, for exampleus for United States.

    The following table lists available hosting jurisdictions and regions for the Apigee control plane.

    Americas

    Control plane hosting jurisdiction descriptionControl plane hosting jurisdiction nameDetails
    United Statesus (multiple regions in United States)Service endpoint:us-apigee.googleapis.com
    Canadaca (multiple regions in Canada)Service endpoint:ca-apigee.googleapis.com
    Consumer data region descriptionConsumer data region nameDetails
    Iowaus-central1leaf iconLow CO2
    Oregonus-west1leaf iconLow CO2
    Los Angelesus-west2
    Salt Lake Cityus-west3
    Las Vegasus-west4
    South Carolinaus-east1
    Northern Virginiaus-east4
    Columbusus-east5
    Dallasus-south1
    Montréalnorthamerica-northeast1leaf iconLow CO2
    Torontonorthamerica-northeast2leaf iconLow CO2

    Europe

    Control plane hosting jurisdiction descriptionControl plane hosting jurisdiction nameDetails
    European Unioneu (multiple regions in the European Union)Service endpoint:eu-apigee.googleapis.com
    Germanyde (multiple regions in Germany)Service endpoint:de-apigee.googleapis.com
    Francefr (single region europe-west9)Service endpoint:fr-apigee.googleapis.com
    Switzerlandch (single region europe-west6)Service endpoint:ch-apigee.googleapis.com
    Consumer data region descriptionConsumer data region nameDetails
    Belgiumeurope-west1leaf iconLow CO2
    Frankfurteurope-west3
    Netherlandseurope-west4
    Zuricheurope-west6leaf iconLow CO2
    Milaneurope-west8
    Pariseurope-west9leaf iconLow CO2
    Turineurope-west12
    Warsaweurope-central2
    Madrideurope-southwest1leaf iconLow CO2
    Finlandeurope-north1leaf iconLow CO2

    Asia-Pacific

    Control plane hosting jurisdiction descriptionControl plane hosting jurisdiction nameDetails
    Australiaau (multiple regions in Australia)Service endpoint:au-apigee.googleapis.com
    Indiain (multiple regions in India)Service endpoint:in-apigee.googleapis.com
    Japanjp (multiple regions in Japan)Service endpoint:jp-apigee.googleapis.com
    Consumer data region descriptionConsumer data region nameDetails
    Sydneyaustralia-southeast1
    Melbourneaustralia-southeast2
    Mumbaiasia-south1
    Delhiasia-south2
    Tokyoasia-northeast1
    Osakaasia-northeast2

    Middle East

    Control plane hosting juridiction descriptionControl plane hosting jurisdiction nameDetails
    Qatarqa (single region me-central1)Service endpoint:qa-apigee.googleapis.com
    Saudi Arabiasa (single region me-central2)Service endpoint:sa-apigee.googleapis.com
    Israelil (single region me-west1)Service endpoint:il-apigee.googleapis.com
    Consumer data region descriptionConsumer data region nameDetails
    Dohame-central1
    Dammamme-central2
    Tel Avivme-west1
  • Consumer data region: You need to specify a region where API consumer data is stored. This must be a sub-region of the control plane region. For a list of available consumer data regions, see Apigee locations.
  • Billing type: You can only use data residency with paid subscription orgs.

Creating an environment using the Apigee API

If you create a new environment using the Apigee API, you must specify thecontrol plane location. SeeCreate an environment.If you use the UI to create an environment, no special steps are needed.

Configure the control planecontractProvider

Add thecontractProvider configuration property to each overrides file and apply the changes. The service endpoint for Apigee management APIs. For example:https://us-apigee.googleapis.com.

For example:

instanceID: "my_hybrid_example"namespace: apigeegcp:  projectID: hybrid-example  region: us-central1k8sCluster:  name: apigee-hybrid  region: us-central1org: hybrid-examplecontractProvider: https://us-apigee.googleapis.com

SeeStep 7: Create the overrides

When calling the Apigee APIs

When you makecurl calls to Apigee APIs to perform tasks in your hybrid installation, you will need to call APIs from within the control plane location:

curl -H "Authorization: Bearer $TOKEN" \  "https://CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/ORG_NAME/envgroups"

For example:

curl -H "Authorization: Bearer $TOKEN" \  "https://us-apigee.googleapis.com/v1/organizations/my-hybrid-org/envgroups"

URL allowlisting

If you are using forward proxies with data residency, you must additionally allowlist in the forward proxy:

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.