[[["易于理解","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-26。"],[[["\u003cp\u003eThis document outlines the necessary ports and communication channels for the Apigee hybrid runtime plane, which is important for enterprise implementations.\u003c/p\u003e\n"],["\u003cp\u003eInternal connections within the hybrid runtime plane use various protocols and ports, with security provided by TLS 1-way and mTLS, to ensure secure communication between components like MART, Cassandra, and Message Processor.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections involve inbound requests from client apps to the Default Istio Ingress and outbound connections from components like Synchronizer, UDCA, and Message Processor to various services, using protocols like OAuth over TLS 1.2.\u003c/p\u003e\n"],["\u003cp\u003eApigee Connect plays a crucial role by facilitating communication between the management plane and the runtime plane via a two-way connection, enhancing the security and efficiency of data exchange.\u003c/p\u003e\n"],["\u003cp\u003eIt is recommended that external connections should not be restricted to specific IP addresses associated with \u003ccode\u003e*.googleapis.com\u003c/code\u003e due to their dynamic nature.\u003c/p\u003e\n"]]],[],null,["# Configure ports and set up firewalls\n\n| You are currently viewing version 1.3 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 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."]]
