[[["易于理解","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\u003eThis document outlines the port usage for the Apigee hybrid runtime plane, which is currently on version 1.1 and is end-of-life.\u003c/p\u003e\n"],["\u003cp\u003eInternal communications within the hybrid runtime plane use a variety of protocols and ports, including TCP 9042/9142 for Cassandra, TCP 8443 for MART and Message Processor interactions, and TCP 7001 for inter-Cassandra node communication, all using mTLS or TLS for security.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections to and from the hybrid runtime plane use ports such as TCP 443 for communications with Apigee Services and GCP, secured with OAuth over TLS 1.2, while client app traffic uses a configurable port secured by None/OAuth over TLS 1.2/mTLS.\u003c/p\u003e\n"],["\u003cp\u003eThe document details outbound connections from components like Message Processor, Synchronizer, UDCA, Prometheus, and fluentd to various external services, including Apigee Services, GCP, and customer-defined backend services.\u003c/p\u003e\n"],["\u003cp\u003eFirewall configurations should avoid relying on specific IP addresses for \u003ccode\u003e*.googleapis.com\u003c/code\u003e due to their dynamic nature, and instead focus on the domain name and relevant ports.\u003c/p\u003e\n"]]],[],null,["# Configure ports and set up firewalls\n\n| You are currently viewing version 1.1 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 any specific IP addresses associated with\n`*.googleapis.com`. The IP addresses can change since the domain currently resolves to\nmultiple addresses."]]