Help Center> Distributed Message Service for RocketMQ> User Guide> Preparing Required Resources
Updated on 2024-05-14 GMT+08:00
View PDF

Preparing Required Resources

Overview

Before purchasing a RocketMQ instance, prepare the required resources, including a virtual private cloud (VPC), subnet, and security group with proper rules. Each RocketMQ instance is deployed in a VPC and bound to a specific subnet and security group, which provide an isolated virtual network environment and allow you to easily configure and manage security protection policies.

Required Resources

Table 1 lists the resources required by a RocketMQ instance.

Table 1 RocketMQ resources

Resource

Requirement

Operations

VPC and subnet

Configure the VPC and subnet for RocketMQ instances as required. You can use the current account's existing VPC and subnet or shared ones, or create new ones.

VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). Through VPC sharing, you can easily configure, operate, and manage multiple accounts' resources at low costs. For more information about VPC and subnet sharing, see VPC Sharing.

Note the following when creating a VPC and a subnet:

  • The VPC and the RocketMQ instance must be in the same region.
  • Use the default settings when creating a VPC and subnet.

For details on how to create a VPC and subnet, see Creating a VPC. If you need to create and use a new subnet in an existing VPC, see Creating a Subnet for the VPC.

Security group

Different RocketMQ instances can use the same security group or different security groups.

To use RocketMQ instances, add the security group rules described in Table 2 or Table 3. You can also add other rules based on site requirements.

NOTE:

After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a RocketMQ instance within a VPC, and do not need to add rules according to Table 2 or Table 3.

For details on how to create a security group, see Creating a Security Group. For details on how to add rules to a security group, see Adding a Security Group Rule.

EIP

Note the following when creating EIPs:

  • The EIPs must be created in the same region as the RocketMQ instance.
  • The RocketMQ console cannot identify IPv6 EIPs.

For details about how to create an EIP, see Assigning an EIP.
Table 2 Security group rules (RocketMQ 4.8.0)

Direction

Protocol

Port

Source

Description

Inbound

TCP

8100

0.0.0.0/0

The port is used for intra-VPC access to metadata nodes.

Inbound

TCP

8200

0.0.0.0/0

The port is used for public access to metadata nodes.

Inbound

TCP

10100-10199

0.0.0.0/0

The port is used for accessing service nodes.
Table 3 Security group rules (RocketMQ 5.x)

Direction

Protocol

Port

Source

Description

Inbound

TCP

8100

0.0.0.0/0

The port is used for private network access to instances using TCP.

Inbound

TCP

8200

0.0.0.0/0

The port is used for public network access to instances using TCP.

Inbound

TCP

10100-10199

0.0.0.0/0

The port is used for accessing service nodes using TCP.

Inbound

TCP

8080

0.0.0.0/0

The port is used for private network access to instances using gRPC.

Inbound

TCP

8081

0.0.0.0/0

The port is used for public network access to instances using gRPC.