Preparation Before Ordering
Before you create a DMS RocketMQ instance, you need to make some preparations.
First, you need to set up a virtual private cloud (VPC), which is an isolated network environment to host the RocketMQ instance.
Next, you need to create a subnet, which is a subnet inside the VPC to separate different parts and regions.
Finally, you need to configure a security group to control inbound and outbound traffic rules to ensure the security of the RocketMQ instance.
Each DMS RocketMQ instance is deployed in a specific VPC and associated with a specific subnet and security group. This allows you to configure and manage the network environment of your RocketMQ instance on your own, and provides security protection policies. If you already have existing VPCs, subnets, and security groups, you can reuse them without having to additional creation. This saves time and resources, and also ensures consistency and reliability.
VPCs and Subnets
VPCs and subnets can be reused, or you can use different VPCs and subnets to configure your RocketMQ instance based on your actual needs. When creating a VPC and a subnet, keep in mind the following requirements:
l The VPC and the associated DMS RocketMQ should be located in the same region.
l If you have no special requirements, you can use the default configuration to create VPCs and subnets.
For operations about how to create a VPC and a subnet, refer to Virtual Private Cloud (VPC) - Creating a VPC and a Subnet, and Building a Private Network.
If you want to create and use a new subnet in an existing VPC, refer to Virtual Private Cloud (VPC) - Subnet Management - Creating a Subnet.
Note:
l To create an IPv4 instance, you only need to configure the IPv4 subnet for the VPC subnet.
l To create an IPv6 instance, you only need to configure the ipv4/ipv6 dual-stack subnet for the VPC subnet.
Security Group
Security groups can be reused, or you can use different security groups and configurations based on your actual needs.
For more operations about how to create a security group, refer to Virtual Private Cloud (VPC) - Creating a Security Group.
If you want to add rules to a security group, refer to Virtual Private Cloud (VPC) - Security Group - Adding a Security Group Rule.
ECS
To connect your client application to RocketMQ to send and consume messages, purchase an ECS and ensure that the ECS is located in the same VPC as the RocketMQ instance. For creation instructions, see Create ECS.
Order Instance
Instance Introduction
You can subscribe to RocketMQ instances with user-defined specifications and features, and deploy them in physically isolated areas. A RocketMQ instance is exclusive to the tenant and can be customized with business-based specifications. On new resource pool nodes, rich options such as selecting host types and storage specifications are also supported for users.
Procedure
1. Click Activate Now on the Product Details page, or on the message management console, create an instance and go to the page for ordering DMS RocketMQ.
2. Create an instance and select the product specification.
(1) Fill in the instance name. You can change the default name.
(2) Select the engine type. By default, the system selects the RocketMQ engine, which is fully compatible with high performance and low latency message queues of open-source clients.
(3) Select a billing mode. There are two billing modes, namely annual/monthly subscription and pay-as-you-go billing. See Billing Modes for details.
(4) The purchase duration varies based on the billing mode you have selected:
l The billing mode is a yearly and monthly subscription, with the option to purchase a duration of 1-6 months and 1-3 years. This mode provides an automatic renewal function. When checked, the purchase duration can be automatically renewed: 1-6 months and 1-3 years.
l The billing mode is pay-as-you-go, this option is hidden from selection.
(5) Deployment mode: single-AZ and multiple-AZ deployment. Currently, only single-AZ and three-AZ deployment are supported. For single-AZ deployment, select any AZ. For multi-AZ deployment, select three AZs, and the system will automatically distribute the broker nodes evenly to each AZ.
(6) Set the number of master-slave node pairs, which can be 2/4/8/12/16. The master-slave nodes refer to the role switching between producers and consumers of a topic. When the master node fails or is unavailable, the slave node automatically takes over the work and continues to provide services. The design of the master-slave nodes ensures the stability and reliability of the system.
(7) Select the host type from the drop-down menu. You can select common or computing-plus. General-purpose cloud server shares the CPU resources of the host, mainly providing basic level of vCPU performance, balanced computing, memory and network resources, with high cost-effectiveness, and supporting general-purpose business operations. Computing-plus cloud server exclusively uses the CPU resources of the host, with no CPU contention between instances and no over-allocation of resources, and is equipped with a new network acceleration engine to achieve strong stability performance close to that of physical server.
(8) Select instance specifications. RocketMQ provides three types of specifications, including common or computing-plus. For details, refer to ECS Specifications.
(9) Select storage space, including disk type and space.
l There are three types of disks available: high I/O, common I/O, and ultra-high I/O. Common I/O is suitable for scenarios with large capacity, medium read/write speeds, and low transaction processing. High I/O is suitable for mainstream high-performance and high-reliability application scenarios. Ultra-high I/O is suitable for read/write-intensive application scenarios with ultra-high IOPS and ultra-high bandwidth requirements. For more information about disk types, see EVS Specifications.
l Disk space starts at 100G and can be increased by a factor of 100.
(10) Select an existing VPC. If no VPC exists, click Create to jump to the VPC page to add one. For more information, refer to VPC.
(11) Select an existing subnet. If no subnet exists, click Create to jump to the subnet page to add one.
(12) Select an existing security group. If no security group exists, click Create to jump to the security group page to add one.
3. After filling in the above information, click Next to enter the fee confirmation page.
4. After confirming that the instance information is correct, submit the request.
On the instance list page, check whether the RocketMQ instance is successfully created. It takes about 3 to 15 minutes to create an instance, and the instance status is Creating.