ApsaraMQ for Kafka:Purchase and deploy ApsaraMQ for Confluent instances

Prerequisites

Before you begin, make sure that you have:

• An Alibaba Cloud account with no overdue payments. To use an ApsaraMQ for Confluent cluster, a specific number of Server Load Balancer (SLB) instances must be purchased.

• The required permissions to access ApsaraMQ for Kafka. For details, see Obtain access permissions.

• A VPC and vSwitch in the target region. Each vSwitch must have more than 64 available IP addresses to support cluster deployment.

Purchase an instance

1. Log on to the ApsaraMQ for Confluent console. In the left-side navigation pane, click Instances.

2. In the top navigation bar, select a region and click Buy Instance.

3. In the panel that appears, set the Instance Version parameter to Confluent and then click OK.Select Instance Billing Method

4. Configure the following parameters and click Create Cluster. Complete the payment as prompted.

   Parameter	Description
   Plan Edition	Edition for the cluster. Available editions: Professional Edition and Enterprise Edition. For a comparison of edition features, see Editions.
   Duration	Subscription duration. Example: 1 year.
   Region and Zone	Region and zone where the cluster runs. Example: China (Hangzhou).
   Computing Resources	Number of capacity units (CUs) for the cluster. Size this based on your expected throughput and retention requirements. For guidance, see Evaluate cluster resources.
   Component Resources	Storage and component configuration for the cluster. Adjust based on the components you plan to use, such as ksqlDB and Connect. For guidance, see Evaluate cluster resources.

   Note

   One capacity unit (CU) = 1 CPU core + 4 GB of memory.

Deploy the instance

After purchase, the instance status is Not Deployed. Deploy it into your VPC to start using it.

1. Log on to the ApsaraMQ for Confluent console. In the left-side navigation pane, click Instances.

2. In the top navigation bar, select the region. Find the instance whose status is Not Deployed and click Deploy in the Actions column.

3. In the Deploy Instance panel, configure the following parameters and click OK.

   Parameters configured when deploying an instance

   Parameter	Description	Example
   Deployment Mode	Select the deployment mode of the cluster. Single-zone and multi-zone deployment are supported.	Single zone
   Zone	Select a zone.	Zone A
   VPC	The virtual private cloud (VPC) in which the SLB instance resides.	vpc-bp17fapfdj0dwzjkd****
   vSwitch	Select a vSwitch. If no vSwitch is created, you must first create a vSwitch in the corresponding zone. To ensure that the cluster can be deployed as expected, specify more than 64 available IP addresses for each vSwitch.	vsw-bp1gbjhj53hdjdkg****
   SLB	By default, SLB is activated.	None
   Assign Public Network IP	Specify whether to enable Internet access for the cluster.	Yes
   Logon Username	By default, Control Center uses the root user.	root
   Logon Password	Set the password for logging on to Control Center.	******
   Confirm Password	Enter the password for the account again.	******

   After you configure the parameters, the instance enters the Deploying state. Deployment takes approximately 10 to 30 minutes.

Upgrade instance configurations

If the instance no longer meets your workload requirements, scale it up:

1. On the Instance Details page, click Upgrade in the upper-right corner.

2. On the Upgrade Confluent page, adjust the component resources and click Upgrade. Complete the payment as prompted.

3. The instance status changes to Upgrading. When the status returns to Running, the upgrade is complete.

Next steps

For information about how to log on to and use Control Center, see Basic usage of Control Center.