Updated on 2023-10-08 GMT+08:00

Step 2: Create a RocketMQ Instance

Your RocketMQ instance will be deployed in physical isolation and exclusively used by you. You can customize the computing capabilities and storage space of an instance based on service requirements.

Prerequisites

Before creating a RocketMQ instance, ensure that a VPC and a security group are available. If no VPC or security group is available, create them by referring to Step 1: Prepare the Environment.

Procedure

  1. Go to the Buy Instance page.
  2. Select a billing mode.
  3. Select a region closest to your application to reduce latency and accelerate access.
  4. Select a project from the drop-down list.
  5. Select one AZ or at least three AZs.
  6. Configure the following instance parameters:

    1. Instance Name: Enter a name for the instance.
    2. Enterprise Project: Select an enterprise project based on service requirements.
    3. Specifications: Select Default or Custom.
      If you select Default and the version is 4.8.0, specify the flavor, number of brokers, and broker storage space to be supported by the RocketMQ instance based on the site requirements.
      • Instance Type: Currently, only cluster instances are supported.
      • CPU Architecture: Currently, only x86 architecture is supported.
      • Broker Flavor: Select the required flavor.
      • Brokers: Select the required number of brokers.
      • Storage Space per Broker: Specify the disk type and storage space of each broker.

        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 Disk Performance.

      Figure 1 Default specifications

      If you select Custom, the system calculates the number of brokers and broker storage space for different flavors based on your specified number of topics, peak creation TPS, peak retrieval TPS, average message size, and number of messages created every day. You can select one of the recommended flavors as required.

      Figure 2 Specification calculation

  7. Configure the instance network parameters.

    1. Select a VPC and a subnet.

      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.

  8. Select the required duration.

    This parameter is displayed only if the billing mode is yearly/monthly.

  9. Click More Settings to configure more parameters.

    1. Configure public access.

      Public access is disabled by default. You can enable it or keep it disabled as required.

      After public access is enabled, configure an IPv4 EIP for each broker.

      Figure 3 Configuring public access
    2. Configure SSL.

      This parameter indicates whether to enable SSL authentication when a client connects to the RocketMQ instance. After SSL is enabled, data will be encrypted before transmission for higher security, but performance will be degraded.

      This setting cannot be changed after the instance is created. If you want to use a different SSL setting after the instance is created, you must create another instance.

    3. 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, by usage, owner, or environment).

      • If you have created predefined tags, select a predefined pair of tag key and value. You can click View predefined tags to go to the Tag Management Service (TMS) console and view or create tags.
      • You can also create new tags by entering Tag key and Tag value.

      Up to 20 tags can be added to each RocketMQ instance.

    4. Enter a description of the instance.

  10. Click Buy.
  11. Confirm the instance information and submit the request.
  12. Return to the instance list and check whether the RocketMQ 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 fails to be created, view Instance Creation Failures. Delete the instance and create another one. If the instance creation fails again, contact customer service.