Buying a RocketMQ Instance

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 specific 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.

Table 1 lists the resources required by a RocketMQ instance.

1. Log in to the console.
2. Click in the upper left corner to select a region.

   DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest region for low latency and fast access.

3. Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
4. Click Buy RocketMQ Instance in the upper right corner of the page.
5. Select Billing Mode.
6. Select a Region.

   DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.

7. Select a Project.

   Projects isolate compute, storage, and network resources across geographical regions. For each region, a preset project is available.

8. Select an AZ.

   An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

   Select AZs as prompted based on the instance version.

9. Enter an Instance Name.

   You can customize a name that complies with the rules: 4–64 characters; starts with a letter; can contain only letters, digits, hyphens (-), and underscores (_).

10. Select an Enterprise Project.

    This parameter is for enterprise users. An enterprise project manages cloud resources. The enterprise project management service unifies cloud resources in projects, and resources and members in a project. The default project is default.

11. Configure the following instance parameters:
    1. Version: Only 4.8.0 and 5.x are available.
    2. Instance Type: Select the basic or professional edition based on your service requirements.

       This parameter is required only for v5.x.

    3. Architecture: Single-node and Cluster are available for v5.x. Cluster is available for v4.8.0.
       • Single-node: There is only one RocketMQ broker. The single-node architecture can only be used for testing.
       • Cluster: There are multiple RocketMQ brokers.
    4. Flavor: Select the required flavor.
    5. Brokers: Select the required number of brokers.

       This parameter is required only for v4.8.0.

    6. Storage Space per Broker/Storage Space: Disk type and total storage space of each broker.

       The disk size must be multiple of 100. The disk type cannot be changed once the RocketMQ instance is created.

       The disk type can be high I/O or ultra-high I/O. For details on how to select a disk type, see "Disk Types and Performance" in Elastic Volume Service User Guide.

       The 5.x professional edition does not support high I/O.

12. Configure the instance network parameters.
    1. Select the created VPC and subnet from the VPC drop-down list.

       A VPC provides an isolated virtual network for your RocketMQ instances. You can configure and manage the network.

       After the RocketMQ instance is created, its VPC and subnet cannot be changed.

    2. Select a security group.

       A security group is a set of rules for accessing a RocketMQ instance.

13. Configure SSL.
    • SSL: Ciphertext access with high security, but lower performance.
    • PLAINTEXT: Plaintext access with high performance, but lower security.
    • PERMISSIVE: Both ciphertext and plaintext access, depending on the client.

    The SSL setting can be changed after the instance is created. Select a transmission mode as required.

14. Configure ACL.

    After ACL is enabled, the permissions for each user are exclusive.

15. Click More Settings to configure more parameters.
    • Configure Public Access.

      Public access is disabled by default. You can enable or disable it as required. After public access is enabled, configure an IPv4 EIP for the RocketMQ instance.

    • Specify tags.

      Tags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify cloud resources by dimension (for example, usage, owner, or environment).

      • If you have created predefined tags, select a predefined pair of tag key and value. To view or create predefined tags, click View predefined tags on the right. You will then be directed to the TMS console.
      • You can also create new tags by entering Tag key and Tag value.

      Up to 20 tags can be added to each RocketMQ instance. For details about the requirements on tags, see Configuring Tags for a RocketMQ Instance.

    • Enter a description of the instance.

16. Click Buy Now.
17. Confirm the instance information, and click Submit.
18. Return to the instance list and check whether the instance has been created.

    It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.

    • If the instance is created successfully, its status changes to Running.
    • If the instance is in the Failed state, delete it by referring to Deleting a RocketMQ Instance and try creating another one. If the instance creation fails again, contact customer service.