Adding Ports, IPs, and Hostnames for Runtime Manager Agent

To enable Runtime Manager agent connectivity in your customer-hosted Mule runtime environment, you must configure your network infrastructure to allow communication with Anypoint Platform APIs and services. This configuration involves adding specific hostnames, ports, and IP addresses to your network allowlists and firewall rules.

These sections provide the specific network configuration details required for each communication protocol and regional deployment.

All connectivity requirements are for outbound connections from your network to Anypoint Platform. No inbound connectivity to your network or servers is required.

Runtime Manager agent establishes persistent WebSocket connections that remain active for ongoing communication with Anypoint Platform services.

This page lists US Cloud, EU Cloud, and MuleSoft Government Cloud endpoints. For Canada Cloud, Japan Cloud, India Cloud, and Australia Cloud, allowlist the Platform URL, analytics ingest, and Runtime Manager hosts in Control Plane Hostnames and Allowlists.

The Runtime Manager agent uses mutual TLS (mTLS) to authenticate directly with these endpoints:

The *.ingest.mulesoft.com endpoints handle OpenTelemetry metrics ingestion.

These endpoints use WebSocket connections for real-time communication between the agent and Runtime Manager. Ensure your firewall supports WebSocket protocol upgrades and persistent connections for these endpoints.

Configure your firewall to allow outbound connections to these ports and hostnames based on your Anypoint Platform region.

For network environments that require IP-based firewall rules, use these static IP addresses to allow Runtime Manager connectivity.

Configure hostname-based firewall rules for Anypoint Platform services that use dynamically assigned IP addresses.