Back to FAQ library

What network connectivity patterns are supported in CloudHub 2.0 Private Spaces?

CloudHub 2.0 Private Spaces provide isolated container environments in AWS with flexible networking topologies:

1. Inbound External Clients

Public internet traffic terminates at the Private Space dedicated Ingress load balancers, with optional TLS termination and path-based routing:

Inbound External Clients

2. Outbound via AWS PrivateLink

Applications connect securely to customer-owned AWS VPC services or partner endpoints without routing traffic over the public internet:

Outbound via AWS PrivateLink

3. Intra-Private Space Communication

Mule apps within the same Private Space communicate securely over internal cluster DNS without traversing public interfaces:

Intra-Private Space Communication

4. Non-HTTP TCP / VPN (e.g. HL7 MLLP)

For legacy protocols such as HL7 MLLP or raw TCP connections, an Anypoint VPN or Direct Connect gateway bridges Private Space subnets directly to on-premises datacenters:

Non-HTTP TCP Connection

Related Links