[[["易于理解","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-29。"],[[["\u003cp\u003eThis document outlines the port usage for internal and external communications within the Apigee hybrid runtime plane, detailing which ports are used for secure connections between services.\u003c/p\u003e\n"],["\u003cp\u003eInternal connections within the hybrid runtime plane use a mix of protocols and ports, including TCP 9042/9142 for Cassandra, TCP 8443 for connections to MART and the management plane, and mTLS for communication with fluentd.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections involve both inbound traffic, such as API requests from client apps to the Default Istio Ingress, and outbound traffic, such as the Synchronizer fetching configuration data from Apigee Services via TCP 443.\u003c/p\u003e\n"],["\u003cp\u003eApigee Connect establishes a two-way connection with Apigee Services over TCP 443 for management data, initiated from within the runtime plane, eliminating the need for firewall configuration for inbound connectivity.\u003c/p\u003e\n"],["\u003cp\u003eThe document mentions version 1.6 of Apigee hybrid is end of life and to upgrade to a newer version.\u003c/p\u003e\n"]]],[],null,["# Secure ports usage\n\n| You are currently viewing version 1.6 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."]]
