Connection Method | Connection Description | 5.x Cluster | 4.x Exclusive Cluster and General Cluster | 4.x Virtual Cluster | Documentation |
Private network connection | If the client and the TDMQ for RocketMQ cluster are deployed in the same Virtual Private Cloud (VPC) network, they can interconnect with each other by default, and no additional configuration is required. | ✓ | ✓ | ✓ | / |
| If the client and the TDMQ for RocketMQ cluster are deployed in different VPC networks, they cannot communicate with each other directly because different VPC networks are logically isolated. To enable VPC networks in different regions under the same account to communicate with each other, use Cloud Connect Network (CCN). | ✓ | ✓ | ✓ | |
Public network connection | A dedicated public network route needs to be configured for clients to connect to the TDMQ for RocketMQ cluster through the public network. Since public networks are accessible from any environment, security policies need to be configured to ensure connection security. | ✓ | ✓ | × | |
Direction | Protocol | Port | Source IP Address | Description |
Inbound | TCP | 8080 | IP address or address group where the TDMQ for RocketMQ client resides. | Port for accessing TDMQ for RocketMQ 5.x clusters using Transmission Control Protocol (TCP). |
Inbound | TCP | 9876 | IP address or address group where the TDMQ for RocketMQ client resides. | Port for accessing TDMQ for RocketMQ 4.x clusters using TCP. |
Inbound | TCP | 5576 | IP address or address group where the TDMQ for RocketMQ client resides. | Port for accessing TDMQ for RocketMQ 4.x clusters using Hypertext Transfer Protocol (HTTP). |
Feedback