Skip to Main Content

Experience AutoMQ for Kafka

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

In this article, references to AutoMQ product service provider, AutoMQ service provider, and AutoMQ specifically refer to AutoMQ HK Limited.

Prerequisites​

Before creating a Kafka instance, you need to meet the prerequisites and ensure that the environment installation 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 operate to create an instance on the environment console front-end interface, and the console back-end will create the underlying cloud resources on behalf of the user and complete the software deployment of the instance.

The operation process is as follows:

  1. Visit the environment console address to enter the environment console.

  2. Enter the environment console, click on the left-side navigation bar, and proceed to the instance list.

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

Parameter
Description
Instance Name
  • Explanation: The instance name is an alias used to distinguish instances. It is user-defined.
  • Restrictions: Refer to Restrictions▸.
Instance Note
  • Explanation: The instance note is a custom description used to distinguish the purpose of the instance, typically inputting the business scenario. It is user-defined.
  • Restrictions: Refer to Restrictions▸.
Availability Zone Information
  • Explanation: AutoMQ for Kafka instances currently support single-zone and three-zone deployments. Choose the appropriate configuration based on business requirements.
  • Options:
    • Single Zone: All nodes of the Kafka cluster are deployed in a single user-specified availability zone.
    • Three Zones: All nodes of the Kafka cluster are evenly distributed across three user-specified availability zones.
Subnet Information
  • Explanation: AutoMQ for Kafka instances currently support setting only one subnet per availability zone. For multi-zone and multi-subnet requirements, please refer to Obtaining Services▸.
  • Options: The user-provided subnet should contain a sufficient number of available IPs (at least 100 recommended) to prevent instance scaling issues due to insufficient IPs in the future.
Compute Specifications
  • Explanation: Compute specifications represent the message throughput capacity of the current AutoMQ Kafka instance. Refer to the product billing instructions and evaluate based on the number of AKUs. For details, refer to Billing Instructions for BYOC▸.
  • Restrictions: The AKU limit for instance creation is version-dependent. For details, refer to Restrictions▸.
Storage Specifications
  • Description: AutoMQ Kafka uses object storage as the message storage medium, so there is no need to reserve storage capacity in advance. Storage is used on-demand and billed based on the actual message capacity during usage.
  1. Click "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, then click on the "Topics" navigation bar on the left.

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

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

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

Next Steps​

The current quick start tutorial only demonstrates the basic process from environment creation to instance creation. AutoMQ Kafka is 100% compatible with Apache Kafka®, so for practical use of AutoMQ Kafka, please refer to the relevant knowledge and documentation of Apache Kafka®.

If there is no business requirement after the quick start and testing, it is recommended to release the environment as soon as possible to avoid underlying cloud resource consumption and potential costs.