[[["易于理解","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 document outlines the port usage for Apigee hybrid version 1.8, which is end-of-life and should be upgraded, detailing both internal and external communication channels.\u003c/p\u003e\n"],["\u003cp\u003eInternal communications within the hybrid runtime plane utilize protocols like TCP and are secured with mTLS or TLS, with certificates managed by Apigee.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections involve inbound traffic to the MART Istio Ingress for API calls and outbound traffic to Apigee Services and Google Cloud for configuration, authorization, analytics, and metrics, generally using TCP port 443 with OAuth over TLS 1.2 or TLS.\u003c/p\u003e\n"],["\u003cp\u003eApigee Connect facilitates two-way communication between the management plane and the runtime plane using TLS over TCP 443, which eliminates the need for inbound firewall configurations for this connection.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections to \u003ccode\u003e*.googleapis.com\u003c/code\u003e should not be limited to specific IP addresses, as these can change and resolve to multiple addresses.\u003c/p\u003e\n"]]],[],null,["# Secure ports usage\n\n| You are currently viewing version 1.8 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\nUnderstanding which ports the hybrid runtime plane uses is important for enterprise\nimplementations. This section describes the ports used for secure communications within the\nruntime plane as well as external ports used for communications with external services.\n\nInternal connections\n--------------------\n\nCommunication between the runtime plane and management plane is secured with TLS 1-way and OAuth\n2.0. Individual services use different protocols, depending on which service they are communicating\nwith.\n\nThe certificates used for intra-component communication are generated by Apigee's certificate\nmanager. You do not have to provide a certificate or manage it.\n\nThe following image shows the ports and communications channels within the hybrid runtime\nplane:\n\nThe following table describes the ports and communications channels within the hybrid runtime\nplane:\n\nExternal connections\n--------------------\n\nTo appropriately configure your network firewall, you should know the inbound and outbound ports\nused by hybrid to communicate with external services.\n\nThe following image shows the ports used for external communications with the hybrid runtime\nplane:\n\nThe following table describes the ports used for external communications with the hybrid runtime\nplane:\n\nYou should not allow external connections for specific IP addresses associated with\n`*.googleapis.com`. The IP addresses can change since the domain currently resolves to\nmultiple addresses."]]
