Understanding which ports the hybrid runtime plane uses is important for enterprise
implementations. This section describes the ports used for secure communications within the
runtime plane as well as external ports used for communications with external services.
Internal connections
Communication between the runtime plane and management plane is secured with TLS 1-way and OAuth
2.0. Individual services use different protocols, depending on which service they are communicating
with.
The following image shows the ports and communications channels within the hybrid runtime
plane:
The following table describes the ports and communications channels within the hybrid runtime
plane:
Internal Connections
Source
Destination
Protocol/Port(s)
Security Protocol
Description
MART
arrow_right_alt
Cassandra
TCP/9042 TCP/9142
mTLS
Sends data for persistence
Apigee Connect
arrow_right_alt
MART
TCP/8443
TLS
Requests from the management plane go through Apigee Connect. Apigee Connect initiates
the connection.
OPTIONAL: MART Istio Ingress Only if not usingApigee Connect
arrow_right_alt
MART
TCP/8443
TLS
Requests from the management plane go through the MART Istio Ingress
Default Istio Ingress
arrow_right_alt
Message Processor
TCP/8443
TLS (Apigee-generated, self-signed cert)
Processes incoming API requests
Message Processor
arrow_right_alt
Cassandra
TCP/9042 TCP/9142
mTLS
Sends data for persistence
Message Processor
arrow_right_alt
fluentd (Analytics)
TCP/20001
mTLS
Streams data to the data collection pod
Cassandra
compare_arrows
Cassandra
TCP/7001
mTLS
Intra-node cluster communications. Note that you can also leave port 7000 open for
firewall configuration as a backup option for potential troubleshooting.
Prometheus
arrow_right_alt
Cassandra
TCP/7070 (HTTPS)
TLS
Scrapes metrics data from various services
MART
TCP/8843 (HTTPS)
TLS
Message Processor
TCP/8843 (HTTPS)
TLS
Synchronizer
TCP/8843 (HTTPS)
TLS
UDCA
TCP/7070 (HTTPS)
TLS
External connections
To appropriately configure your network firewall, you should know the inbound and outbound ports
used by hybrid to communicate with external services.
The following image shows the ports used for external communications with the hybrid runtime
plane:
The following table describes the ports used for external communications with the hybrid runtime
plane:
* indicates that the port is configurable. Apigee recommends using 443.
Two-way Connections
Apigee Connect
compare_arrows
Apigee Services
TCP/443
TLS
Communicates management data between the managemennt plane and the Management API for
Runtime data (MART) in the runtime plane. Apigee Connect initiates the connection;
connects toapigeeconnect.googleapis.com
You should not allow external connections for specific IP addresses associated with*.googleapis.com. The IP addresses can change since the domain currently resolves to
multiple addresses.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis document outlines the various ports and communication channels used by the Apigee hybrid runtime plane for both internal and external connections.\u003c/p\u003e\n"],["\u003cp\u003eInternal communication within the runtime plane uses protocols like mTLS and TLS, with specific ports for services like Cassandra (TCP/9042, TCP/9142), and message processor to analytics (TCP/20001).\u003c/p\u003e\n"],["\u003cp\u003eExternal connections involve inbound traffic, such as API requests from client apps through the default Istio Ingress, and outbound traffic, including data sent from the synchronizer, UDCA, and other components to Apigee services and GCP (all using TCP/443).\u003c/p\u003e\n"],["\u003cp\u003eApigee Connect facilitates communication between the runtime plane and management plane through TCP/443 using TLS, initiating the connection itself.\u003c/p\u003e\n"],["\u003cp\u003eIt is recommended not to allow external connections for specific IP addresses associated with \u003ccode\u003e*.googleapis.com\u003c/code\u003e, as the resolved IP addresses can change.\u003c/p\u003e\n"]]],[],null,["# Configure ports and set up firewalls\n\n| You are currently viewing version 1.4 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."]]
