[[["易于理解","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-28。"],[[["\u003cp\u003eThis page details the various geographical locations and jurisdictions available for Apigee and Apigee hybrid resources, including runtime infrastructure, API Analytics data, and control planes.\u003c/p\u003e\n"],["\u003cp\u003eThe selection of a region for Apigee resources is crucial, as it impacts latency, availability, durability, and cost, especially when integrating with other Google Cloud services.\u003c/p\u003e\n"],["\u003cp\u003eApigee allows for the selection of runtime regions during the provisioning of an Apigee instance, through either the provisioning wizard, the Apigee UI in Cloud Console, or via API, depending on organization type.\u003c/p\u003e\n"],["\u003cp\u003eApigee API Analytics data storage regions are also configurable during organization provisioning, with options and methods for selection similar to runtime region configuration.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee control plane hosting jurisdiction can be selected when provisioning, and it determines the API host name and data storage location, offering globally or regionally based options, such as \u003ccode\u003eus-apigee.googleapis.com\u003c/code\u003e or \u003ccode\u003eeu-apigee.googleapis.com\u003c/code\u003e, respectively.\u003c/p\u003e\n"]]],[],null,["# Apigee locations\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nApigee organization resources can be created in many [locations](/about/locations).\nThese locations represent the geographical *regions* where Apigee resources, such as the Apigee runtime infrastructure and Apigee API Analytics data, are stored and accessed. Google manages these resources so that\nthey are available redundantly in [all zones within that region](/docs/geography-and-regions).\n\nMeeting your latency, availability, or durability requirements are primary factors for selecting the\nregion where your Apigee resources are located. You should consider the locations where Apigee\nis available and the [locations](/about/locations#region) of the other Google Cloud\nproducts and services that Apigee may use. Using services across multiple locations can affect Apigee's\nlatency and its [pricing](/apigee/pricing).\n\nSelect a runtime region\n-----------------------\n\nYou select the Apigee runtime hosting region when you provision your Apigee instance. You can select the runtime\nregion when you provision using the [Apigee UI in Cloud console](https://console.cloud.google.com/apigee) or using the API. The following resources outline the steps required to select a runtime hosting region, based on your organization type:\n\nAvailable Apigee runtime regions\n--------------------------------\n\n\nThe following table lists available regions for the Apigee runtime. \n\n### Americas\n\n### Europe\n\n### Asia-Pacific\n\n### Middle East\n\n### Africa\n\nSelect an Apigee API Analytics region\n-------------------------------------\n\nYou select the region where your Apigee API Analytics data is stored when you provision your Apigee organization. You can select the runtime\nregion when you provision using the [Apigee UI in Cloud console](https://console.cloud.google.com/apigee) or using the API. The following resources outline the steps required to select an Apigee API Analytics region, based on your organization type:\n\nAvailable Apigee API Analytics regions\n--------------------------------------\n\nThe following table lists available regions for Apigee API Analytics. \n\n### Americas\n\n### Europe\n\n### Asia-Pacific\n\n### Middle East\n\n### Africa\n\nSelect an Apigee API control plane hosting jurisdiction\n-------------------------------------------------------\n\nYou select the specific Apigee control plane hosting jurisdiction where your data is stored when you provision your\nApigee instance. Note that a jurisdiction refers to a location within a geopolitical boundary that\nmay span more than one region.\n\nYou can select the control plane hosting jurisdiction when you provision using the Apigee UI in Google Cloud console,\nor using the API. The following\nresources outline the steps required to select a control plane hosting jurisdiction, based\non your organization type:\n\nAvailable Apigee API control plane hosting jurisdictions\n--------------------------------------------------------\n\n\nThe Apigee control plane directly binds to the API host name.\n`apigee.googleapis.com` has a global control plane; if you want\nto use a regionalized control plane, the API host name is\n\u003cvar translate=\"no\"\u003eCONTROL_PLANE_LOCATION\u003c/var\u003e`-apigee.googleapis.com`. See\n[Data residency service endpoint](/apigee/docs/api-platform/get-started/drz-concepts#data-residency-service-endpoint) for more information.\n\n\nThe 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"]]
二氧化碳排放量低