[[["易于理解","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-27。"],[[["\u003cp\u003eData residency in Apigee allows you to specify geographic regions for storing Apigee data, ensuring compliance and regulatory requirements are met by storing all customer content in the selected control plane location.\u003c/p\u003e\n"],["\u003cp\u003eData residency with Apigee hybrid is only available for new installations starting with hybrid version 1.12, and it doesn't support Apigee API analytics or the Debug tool.\u003c/p\u003e\n"],["\u003cp\u003eSetting up an Apigee organization with data residency requires the specification of a control plane location for storing core content and a consumer data region for API consumer data, both of which are located within the control plane.\u003c/p\u003e\n"],["\u003cp\u003eData residency can only be used with paid subscription orgs and all environments created must be within the specified control plane location.\u003c/p\u003e\n"],["\u003cp\u003eWhen using data residency, the \u003ccode\u003econtractProvider\u003c/code\u003e configuration property must be added to each overrides file, and \u003ccode\u003ecurl\u003c/code\u003e calls to Apigee APIs must be made within the designated control plane location, while also ensuring that the control plane location URL is allowlisted for forward proxy configurations.\u003c/p\u003e\n"]]],[],null,["# Using data residency with Apigee hybrid\n\n| You are currently viewing version 1.12 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nOverview\n--------\n\n\nData residency for Apigee 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.\n\nFor an overview of data residency for Apigee, see [Introduction to data residency](/apigee/docs/api-platform/get-started/drz-concepts).\n\nData residency with Apigee hybrid\n---------------------------------\n\n| **Note:** [Apigee API analytics](/apigee/docs/api-platform/analytics/analytics-services-overview) and the [Debug tool](/apigee/docs/api-platform/debug/trace-overview) are not supported in Apigee hybrid organizations with data residency enabled.\n\nStarting with hybrid version 1.12, you can use Data residency with new Apigee hybrid installations. You cannot convert an existing installation to use data residency.\n\n### When creating your Apigee org\n\n\nCreating your Apigee organization using data residency requires the following differences. See [Step 2: Create an organization](/apigee/docs/hybrid/v1.12/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### When creating environments\n\n\nWhen creating environments in and installation using data residency, you must create them in the control plane location. See [Step 3: Create an environment group](/apigee/docs/hybrid/v1.12/precog-add-environment).\n\n### Overrides file adjustments\n\n\nWhen using data residency, you must add the [`contractProvider`](/apigee/docs/hybrid/v1.12/config-prop-ref#contractprovider) configuration property to each overrides file and point it to the path for APIs in the control plane location. For 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\n```\n\nSee [Step 6: Create the overrides](/apigee/docs/hybrid/v1.12/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. For example: \n\n```\ncurl -H \"Authorization: Bearer $TOKEN\" \\\n \"https://$CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/$ORG_NAME/envgroups\"\n```\n\nor \n\n```\ncurl -H \"Authorization: Bearer $TOKEN\" \\\n \"https://us-apigee.googleapis.com/v1/organizations/my-hybrid-org/envgroups\"\n```\n| **Note:** If you are using forward proxy with data residency, you must allowlist: \u003cvar translate=\"no\"\u003eCONTROL_PLANE_LOCATION\u003c/var\u003e`-apigee.googleapis.com` for each control plane location.\n|\n| If your security protocols permit, you can allowlist `*-apigee.googleapis.com`\n|\n| For a list of specific URLs required by Apigee hybrid, see [Google Cloud URLs to allow for Hybrid](/apigee/docs/hybrid/v1.12/allow-gcp-urls)."]]
二氧化碳排放量低