[[["易于理解","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 documentation outlines the necessary ports for secure communication within the Apigee hybrid runtime plane and with external services, crucial for enterprise implementations.\u003c/p\u003e\n"],["\u003cp\u003eInternal connections within the runtime plane utilize TLS 1-way and OAuth 2.0 for security, with certificates managed by Apigee's certificate manager, and specific protocols like TCP are used for various services like Cassandra, fluentd, and message processors.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections involve both inbound and outbound traffic, where inbound connections include API requests from client apps and optional hybrid API calls from the management plane, whereas outbound connections involve sending data to various services like Google Cloud, Apigee services, and backend services.\u003c/p\u003e\n"],["\u003cp\u003eApigee Connect facilitates secure two-way communication between the management plane and the runtime plane (MART) over TCP/443, initiated by Apigee Connect, eliminating the need for inbound firewall configurations for this connection.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation emphasizes avoiding external connections based on specific IP addresses associated with \u003ccode\u003e*.googleapis.com\u003c/code\u003e due to the dynamic nature of these IP addresses.\u003c/p\u003e\n"]]],[],null,["# Secure ports usage\n\n| You are currently viewing version 1.11 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."]]
