Preparing Required Resources
Overview
Before creating 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.
Resource |
Requirement |
Operations |
---|---|---|
VPC and subnet |
Different RocketMQ instances can use the same or different VPCs and subnets based on site requirements. Note the following when creating a VPC and subnet:
|
For details about how to create a VPC and subnet, see the Virtual Private Cloud User Guide. |
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. 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. |
For details about how to create a security group and configure security group rules, see the Virtual Private Cloud User Guide. |
EIP |
Note the following when creating EIPs:
|
For details about how to create an EIP, see "Assigning an EIP" in Elastic IP User Guide. |
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. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot