[[["易于理解","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-25。"],[[["\u003cp\u003eThe hybrid runtime plane uses specific ports for secure internal communication between its components, with services utilizing various protocols including TLS and mTLS, and the certificates for these internal connections are managed by Apigee.\u003c/p\u003e\n"],["\u003cp\u003eInternal connections include data persistence through Cassandra, management plane requests via Apigee Connect, API request processing by the Message Processor, data streaming to fluentd, and metrics data collection via Prometheus, among others.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections are used for inbound API requests from clients to the Default Istio Ingress, and for outbound communication to backend services, Apigee Services, Google Cloud, and optionally to a Distributed Trace back end.\u003c/p\u003e\n"],["\u003cp\u003eSynchronizer, UDCA, Apigee Connect, Prometheus, and fluentd components use outbound connections to communicate with Apigee Services or Google Cloud, while the MART also uses outbound connections to connect to Google Cloud for authorization.\u003c/p\u003e\n"],["\u003cp\u003eTwo-way communication between the Apigee Connect and Apigee Services, which use port TCP/443 over TLS, handles management data flow, but firewall configuration for inbound connectivity is not needed due to the connection initiation from Apigee Connect.\u003c/p\u003e\n"]]],[],null,["# Secure ports usage\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. 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."]]
