Skip to Main Content

Experience AutoMQ for Kafka

After completing the environment setup and related initialization, this article explains how to quickly create a Kafka instance and experience message sending and receiving.

In this article, the terms AutoMQ product service provider, AutoMQ service provider, and AutoMQ all specifically refer to AutoMQ HK Limited.

Prerequisites​

Before creating a Kafka instance, you need to meet the prerequisites and ensure that the environment setup is complete. If not, refer to the operations here:

Create Instance​

To experience AutoMQ for Kafka, you first need to create an instance. Each instance can correspond to an open-source Apache Kafka cluster. Users create instances through the front-end interface of the environment console, and the back-end of the console will create the underlying cloud resources and complete the software deployment of the instance on behalf of the user.

The steps are as follows:

  1. Visit the environment console URL and enter the environment console.

  2. Enter the environment console, click the left navigation bar, and go to the instance list.

  3. Click the "Create Instance" button and choose parameters according to the following specifications.

Parameter
Value Description
Instance Name
  • Description: The instance name is an alias used to distinguish instances. User-defined input.
  • Restrictions: Refer to Restrictions▸ .
Instance Note
  • Description: Instance notes are user-defined descriptions used to distinguish the purposes of instances, usually inputting the business scenario. User-defined input.
  • Restrictions: Refer to Restrictions▸ .
Zone Information
  • Description: AutoMQ for Kafka instances currently support deployment in a single zone and three zones. Please choose the appropriate form based on business characteristics.
  • Options:
    • Single Zone: All nodes of the Kafka cluster are deployed in the user-specified single zone.
    • Three Zones: All nodes of the Kafka cluster are evenly distributed in the user-specified three zones.
Subnet Information
  • Description: AutoMQ for Kafka instances currently support setting only one subnet in each available zone. If you have demands for multiple zones and subnets, please refer to Obtaining Services▸ .
  • Options: The user-provided subnet should contain enough available IPs (recommended at least 100) to prevent the risk of instance scaling failure due to insufficient IPs in the future.
Compute Specifications
  • Description: Compute specifications represent the message throughput capability of the current AutoMQ Kafka instance, which can be evaluated based on the number of AKUs as per the product billing instructions. For details, refer to Billing Instructions for BYOC▸ .
  • Restrictions: The AKU upper limit for creating an instance is version-dependent. For details, refer to Restrictions▸ .
Storage Specifications
  • Note: AutoMQ Kafka uses object storage as the message storage medium, so there is no need to reserve storage capacity in advance. Storage is used and billed based on actual message capacity on a pay-as-you-go basis.
  1. Click on "Create Instance" and wait for the instance to be created.

Experience Message Sending and Receiving​

After the instance is created, you need to create a Topic before experiencing simple message sending and receiving. The steps are as follows:

  1. Click on "Instance Details" to enter the instance, and then click on the "Topics" navigation bar on the left.

  2. Click on "New Topic," fill in the relevant parameters, and create the Topic.

  1. Click on the Topic name to enter the Topic details, and then click on the "Produce Message" tab.

  2. Fill in the test message content and click "Send" to complete the functionality experience.

Next Steps​

This quick start guide only demonstrates the basic process from environment creation to instance creation. AutoMQ Kafka is 100% compatible with Apache Kafka®, so for actual usage of AutoMQ Kafka, please refer to the relevant knowledge and documentation of Apache Kafka.

If there are no business requirements after the quick experience and testing, it is recommended to release the environment promptly to avoid unnecessary cloud resource consumption and incurring costs.