Connection Method | Connection Instructions | Managed Edition clusters | Serverless Edition Cluster | Reference Documentation |
Connection via the private network | If the client and the RabbitMQ cluster are deployed in the same Virtual Private Cloud (VPC) network, the network is interconnected by default without requiring additional configuration. | ✓ | ✓ | |
| If the client and the RabbitMQ cluster are deployed in different VPC networks, since VPC networks are logically isolated from each other, they cannot communicate directly. To enable cross-network communication, you can use Cloud Connect Network (CCN) to achieve VPC interconnection across different regions under the same account. | ✓ | ✓ | |
Connection via the public network | A dedicated public network route needs to be enabled, allowing clients to connect to the RabbitMQ cluster via the public network. Since public networks are accessible from any environment, security policies need to be configured to ensure connection security. | ✓ | × | |
Direction | Type | Protocol | Port | Source IP Address | Description |
Inbound | IPv4 | TCP | 5672 | IP address or address group of the RabbitMQ client | Clients access RabbitMQ instances using IPv4 addresses (with SSL encryption disabled). |
Inbound | IPv4 | TCP | 5671 | IP address or address group of the RabbitMQ client | Clients access RabbitMQ instances using IPv4 addresses (with SSL encryption enabled). |
Inbound | IPv4 | TCP | 15672 | IP address or address group of the RabbitMQ client | Access the URL of the web UI page (with SSL encryption disabled). |
Inbound | IPv4 | TCP | 15671 | IP address or address group of the RabbitMQ client | Access the URL of the web UI page (with SSL encryption enabled) |
Inbound | IPv4 | TCP | 15692 | IP address or address group of the RabbitMQ client | Connecting to Prometheus |
Feedback