[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-29。"],[[["\u003cp\u003eData residency in Apigee hybrid installations, available from version 1.12 onward, allows for specifying geographic locations for data storage to meet compliance and regulatory requirements.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring data residency requires creating a new Apigee organization, specifying a control plane location for core content and a consumer data region for API consumer data.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating an environment using the Apigee API with data residency, the control plane location must be specified, while creating it via the UI does not require this.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the new data pipeline feature is mandatory for data residency organizations, allowing analytics and debug data to be sent to the Apigee control plane.\u003c/p\u003e\n"],["\u003cp\u003eThe overrides files must be updated with properties such as the control plane service endpoint and enabling the new data pipeline to ensure data residency is correctly configured.\u003c/p\u003e\n"]]],[],null,["# Using data residency with Apigee hybrid\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis topic explains how to configure a new Apigee hybrid installation for data residency\ncompliance.\n\nAbout data residency\n--------------------\n\nStarting with hybrid version 1.12, you can use data residency with new Apigee\nhybrid installations. You cannot convert an existing installation to use data residency.\n\n\nData residency meets compliance and regulatory requirements by allowing you to specify\nthe geographic locations (regions) where Apigee data is stored. With data residency, selecting\nthe control plane location ensures that all customer content is stored within the specified region.\nSee also, see [Introduction to data residency](/apigee/docs/api-platform/get-started/drz-concepts).\n\nBasic steps for data residency configuration\n--------------------------------------------\n\nTo configure Apigee hybrid for data residency, you need to follow a few basic steps, including:\n\n- [Creating an Apigee organization with data residency](#creatinganorg)\n- [Creating an environment using the Apigee API](#createinganenv)\n- [Enabling the new data pipeline](#newpipeline)\n- [Configuring the overrides file(s)](#configureoverrides)\n\n### Creating an Apigee organization with data residency\n\nWhen you create an Apigee organization, you have the option of enabling the org with\ndata residency. Creating an org with data residency requires you to specify two\nkey location attributes: the **control plane location** and the **consumer data region** .\nYou will also need to specify the **billing type** . For details, see\n[Step 2: Create an organization](/apigee/docs/hybrid/v1.14/precog-provision).\n\n- **Control plane location** : You need to specify the location where customer core content like proxy bundles are stored. For a list see [Available Apigee API control plane regions](/apigee/docs/locations#available-apigee-api-control-plane-regions).\n\n\n The control plane location is the location of the service endpoint location, for example `us` for United States.\n\n\n The following table lists available hosting jurisdictions and regions for the Apigee control plane. \n\n ### Americas\n\n ### Europe\n\n ### Asia-Pacific\n\n ### Middle East\n\n- **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](/apigee/docs/locations#consumer-data-region).\n- **Billing type**: You can only use data residency with paid subscription orgs.\n\n### Creating an environment using the Apigee API\n\n\nIf you create a new environment using the Apigee API, you must specify the\ncontrol plane location. See [Create an environment](./precog-add-environment#apigee-apit).\nIf you use the UI to create an environment, no special steps are needed.\n\n### Enabling the new data pipeline\n\nWhen data residency is enabled for a new hybrid v1.13 organization, you must enable the new data pipeline\nfeature. This feature enables analytics and debug data to be sent to the Apigee control plane. To\nenable the data pipeline, follow the instructions in\n[Configure hybrid to use the new data pipeline](/apigee/docs/hybrid/v1.14/data-collection-with-data-residency).\n\n`newDataPipeline.debugSession` and `newDataPipeline.analytics` are set to `true` by default in hybrid v1.14.0 and later. You will not need to explicitly set these values unless you have previously set them to `false`.\n\n#### Overrides changes to enable the new data pipeline\n\n\nAdd the following configuration properties to each overrides file and apply them:\n\n- [contractProvider](/apigee/docs/hybrid/v1.14/config-prop-ref#contractprovider): The service endpoint for Apigee management APIs. For example: `https://us-apigee.googleapis.com`.\n- [newDataPipeline.debugSession](/apigee/docs/hybrid/v1.14/config-prop-ref#newdatapipeline): Set this to `true` to use the new data pipeline.\n- [newDataPipeline.analytics](/apigee/docs/hybrid/v1.14/config-prop-ref#newdatapipeline): Set this to `true` to enable analytics to use the new data pipeline.\n\nFor example: \n\n```\ninstanceID: \"my_hybrid_example\"\nnamespace: apigee\n\ngcp:\n projectID: hybrid-example\n region: us-central1\n\nk8sCluster:\n name: apigee-hybrid\n region: us-central1\n\norg: hybrid-example\n\ncontractProvider: https://us-apigee.googleapis.com\nnewDataPipeline:\n debugSession: true\n analytics: true\n```\n\nSee [Step 6: Create the overrides](/apigee/docs/hybrid/v1.14/install-create-overrides)\n\n### When calling the Apigee APIs\n\nWhen you make `curl` calls to Apigee APIs to perform tasks in your hybrid installation, you will need to call APIs from within the control plane location: \n\n```\ncurl -H \"Authorization: Bearer $TOKEN\" \\\n \"https://CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/ORG_NAME/envgroups\"\n```\n\nFor example: \n\n```\ncurl -H \"Authorization: Bearer $TOKEN\" \\\n \"https://us-apigee.googleapis.com/v1/organizations/my-hybrid-org/envgroups\"\n```\n\n### URL allowlisting\n\nIf you are using forward proxies with data residency, you must additionally allowlist in the forward proxy:\n\n- \u003cvar translate=\"no\"\u003eCONTROL_PLANE_LOCATION\u003c/var\u003e`-apigee.googleapis.com`\n- \u003cvar translate=\"no\"\u003eANALYTICS_REGION\u003c/var\u003e`-pubsub.googleapis.com`\n- URLs required by Apigee hybrid, see [Google Cloud URLs to allow for Hybrid](/apigee/docs/hybrid/v1.14/allow-gcp-urls).\n\n### Enable analytics and debug data collection with data residency\n\nTo enable analytics and debug data collection, follow the instructions\nin [Configure hybrid to use the new data pipeline](/apigee/docs/hybrid/v1.14/data-collection-with-data-residency)."]]
二氧化碳排放量低