Install Env Via Huawei Marketplace

Refer to Overview▸, using AutoMQ Cloud requires setting up the environment first. This article explains how to install the BYOC environment from the Huawei Cloud Marketplace.

In this article, references to AutoMQ Product Services, AutoMQ Services, and AutoMQ specifically refer to AutoMQ HK Limited and its affiliates.

Prerequisites: Prepare VPC

The AutoMQ BYOC environment is deployed within the user's VPC to ensure data privacy and security. When installing the AutoMQ environment via the Cloud Marketplace, the following two methods are supported:

• Automatically create a new VPC installation environment: Selecting this option allows the installer to automatically create the VPC and other resources without manual configuration, recommended for initial POC and testing.

• User-Provided VPC Installation Environment: The installer will not proactively create a VPC network. Users must specify the existing VPC network and subnet information.

If you select User-Provided VPC Installation Environment, it is recommended to create a VPC with at least 3 availability zones; otherwise, you cannot create a three-availability zone instance later.

Procedure

Step 1: Install AutoMQ from the Huawei Cloud Marketplace

1. Access the AutoMQ product link. AutoMQ Cloud BYOC environment on AWS is distributed through the cloud marketplace product. Users can subscribe to AutoMQ from the Cloud Marketplace. The product link is AutoMQ for Kafka BYOC Version (Console).

2. Select the desired target region, and click Buy Now.

Due to the configuration issues of the marketplace product template, the Instance Configuration and Purchase Method parameters on the product page do not need attention and can be set to their default values.

Instance Type: The instance type for deploying the AutoMQ environment console can be customized in the next step deployment template.

Paid Type: Currently, only pay-as-you-go hourly billing is supported. Monthly billing is not supported at this time.

3. Follow the instructions to agree to the user agreement and authorization, then click use configuration template to activate.

4. Follow the instructions to fill in the installation template parameters. Generate the deployment plan. The parameters that need to be set are detailed in the table below.

Parameter Settings	Value Description
Environment ID	Description: The prefix for the naming of the current RFS stack and its internal resources. Restriction: This name will be used for naming resource variables. It is recommended to use only uppercase and lowercase letters and numbers.
Create New VPC	Description: Specifies whether to create a new VPC for deploying AutoMQ. It is recommended to use a new VPC for POC scenarios and to use the application's VPC for production scenarios. Default value: true
VPC ID	Description: Specifies the target VPC ID for environment deployment. This needs to be set only if Create New VPC parameter is set to false.
Public Subnet ID	Description: Specifies the target subnet ID for environment deployment. This parameter must be set only if the VPC ID parameter is set, meaning when using an existing VPC.
Console CIDR	Description: Set the source CIDR for the security group that accesses the AutoMQ environment console. Default value: 0.0.0.0/0, allowing access from all addresses.
Data OBS Bucket	Description: Set the name of the OBS bucket for storing messages. This bucket is used to store Kafka message data. If not set, a new OBS bucket will be automatically created.
Maintenance OBS Bucket	Description: Set the name of the OBS bucket for maintenance data. This OBS bucket is used to store AutoMQ's system logs, metrics, etc., excluding application data. If not set, a new OBS bucket will be automatically created.
ECS Instance Type	Description: Set the ECS instance type for deploying the AutoMQ BYOC environment console. Limit: It is recommended to choose at least a 2-core, 8GB model.
Cluster Deployment Type	Description: This setting determines whether to install the AutoMQ data cluster on K8s or VM. Options: vm: With this option, the AutoMQ cluster will be installed on ECS by default. k8s: With this option, you will need to configure the CCE cluster as per Deploy to Huawei Cloud CCE▸, and the AutoMQ cluster will be installed on the user-provided CCE.

It is recommended to preview the parameters configured in the previous step and confirm their correctness before creating the execution plan.

5. After generating the execution plan, click Deploy Now.

6. Enter the Environment Console, log in using the initial username and password output by the RFS console, and change it to a custom password.

Note: When copying and pasting output variables from the Huawei Cloud RFS console using the mouse, it is recommended to paste them into a text editor first to avoid hidden characters that might lead to incorrect password input.

Step 2: Complete BYOC Environment Ops Authorization

The BYOC environment is deployed within the user's VPC, ensuring data security and privacy isolation. However, system logs, metrics, and other non-business-related system data will be generated within the BYOC environment. Once the environment installation is complete, users need to refer to Manage Environment Ops Authing▸ to provide the necessary operational authorization to the AutoMQ service provider for system stability monitoring and fault self-healing operations.

Next Steps

Once the environment installation is complete, you can access and use the environment through the following methods supported by AutoMQ:

• Using AutoMQ with Terraform: After the environment installation is complete, users can manage and use AutoMQ through the AutoMQ Terraform Provider. For details on using AutoMQ with Terraform, please refer to the documentation.

• Using AutoMQ via WebUI: Access the console address through a browser, enter the initial username and password to enter the environment console, create instances, and experience product features. Experience AutoMQ for Kafka▸