Help Center/ Distributed Message Service for RocketMQ/ Developer Guide/ Overview
Updated on 2026-08-19 GMT+08:00
View PDF
Share

Overview

This document describes how to collect instance connection information, such as the instance connection address and topic name. It also provides examples of accessing an instance in Java, Go, and Python.

Client Network Environment

A client can access a RocketMQ instance in any of the following modes:

  • If the client runs on an ECS and is in the same region and VPC as the RocketMQ instance, the client can access the instance using a private network IP address.
  • If the client runs on an ECS and is in the same region as the RocketMQ instance but in a different VPC, the client can access the instance across VPCs using a VPC peering connection. For details, see VPC Peering Connection.
  • If the client is not in the same network environment or region as the RocketMQ instance, the client can access the instance using a public IP address.

    For public network access, modify the security group of the RocketMQ instance to ensure that port 8200 (TCP) or 8081 (gRPC) can be accessed from the external network.

If the connection times out or fails, check the network connectivity. You can use Telnet to check connectivity of the connection address and port number of the instance.