Skip to Main Content

Experience AutoMQ for Kafka

After completing the environment setup and initialization, this article demonstrates 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, ensure you have met the prerequisites and completed the environment installation. If not, follow the steps here:

Creating an Instance​

To experience AutoMQ for Kafka, you need to create an instance first. Each instance corresponds to an open-source Apache Kafka cluster. Users can create instances through the front-end interface of the environment console, while the backend 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. Access the environment console URL and enter the environment console.

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

  3. Click the "Create New Instance" button and select 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 Remarks
  • Description: Instance remarks are custom descriptions used to distinguish the purpose of instances, generally inputting business scenarios. User-defined input.
  • Restrictions: Refer to Restrictions▸ .
Availability Zone Information
  • Description: AutoMQ for Kafka instances currently support single-zone and three-zone deployment. Choose the appropriate type based on your business characteristics.
  • Options:
    • Single Availability Zone: All nodes of the Kafka cluster are deployed within the user-specified single availability zone.
    • Three Availability Zones: All nodes of the Kafka cluster are evenly distributed across the user-specified three availability zones.
Subnet Information
  • Description: AutoMQ for Kafka instances currently support setting only one subnet per availability zone. If you have multi-zone and subnet requirements, please refer to Obtaining Services▸ .
  • Options: The subnet provided by the user should contain sufficient available IPs (at least 100 recommended) to prevent future risks of instance expansion failure due to insufficient IPs.
Compute Specifications
  • Description: 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 upper limit for creating instances is subject to version restrictions. For details, refer to Restrictions▸ .
Storage Specifications
  • Description: AutoMQ Kafka uses object storage as the message storage medium. Therefore, there is no need to pre-allocate storage capacity. Usage is based on the actual message volume, with on-demand usage and pay-as-you-go pricing.
  1. Click "Create Instance" and wait for the instance creation to complete.

Experience Sending and Receiving Messages​

After the instance is created, you need to create a Topic before experiencing simple message sending and receiving. Follow these steps:

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

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

  1. Click 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​

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 Apache Kafka documentation and knowledge base.

If there is no business need after the quick experience and testing, it is recommended to release the environment as soon as possible to avoid incurring costs from underlying cloud resource consumption.