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
MART Istio Ingress
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.
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 port usage for secure communication within the Apigee hybrid runtime plane and with external services, which is crucial for enterprise deployments.\u003c/p\u003e\n"],["\u003cp\u003eInternal connections within the hybrid runtime plane utilize various protocols and ports, with security measures like mTLS and TLS, facilitating communication between services like MART, Message Processor, Cassandra, and others.\u003c/p\u003e\n"],["\u003cp\u003eExternal connections involve both inbound (exposed externally) and outbound communication, with Apigee services, client apps, backend services, and GCP services all communicating on various ports and protocols.\u003c/p\u003e\n"],["\u003cp\u003eThe document stresses not to allow external connections for specific IP addresses associated with \u003ccode\u003e*.googleapis.com\u003c/code\u003e, as these can change and resolve to multiple addresses.\u003c/p\u003e\n"],["\u003cp\u003eVersion 1.2 of this documentation is end of life, and it is recommended that you should upgrade to a newer version, as per the provided link.\u003c/p\u003e\n"]]],[],null,["# Configure ports and set up firewalls\n\n| You are currently viewing version 1.2 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."]]
