Skip to Main Content

Runs on MinIO

AutoMQ utilizes S3 storage, with MinIO supporting the S3 access protocol, making it an ideal storage backend for AutoMQ. Below is a guide for deploying AutoMQ using MinIO.

Prerequisites

Acquire Access Credentials and Bucket

Acquire Access Credentials

Access Key and Secret Key refer to the environment variables MINIO_ROOT_USER and MINIO_ROOT_PASSWORD needed for installing MinIO.

Users can query the endpoint using the following command, with the output format as follows:


sudo systemctl status minio.service


API: http://10.1.0.240:9000 http://172.16.1.104:9000 http://172.16.1.103:9000 http://172.16.1.102:9000

Creating a MinIO Bucket

  1. You can configure the necessary AWS CLI Access Key and Secret Key by setting environment variables.

export AWS_ACCESS_KEY_ID=minioadmin
export AWS_SECRET_ACCESS_KEY=minio-secret-key-CHANGE-ME

  1. Use AWS CLI to create an S3 bucket.

aws s3api create-bucket --bucket automq-data --endpoint=http://10.1.0.240:9000

Fetching Configuration Information

After creating users and Buckets, you can gather the necessary configuration information for deploying AutoMQ.

Parameter Name
Default Value in This Example
Description
KAFKA_S3_ACCESS_KEY
minioadmin
Environment variable MINIO_ROOT_USER
KAFKA_S3_SECRET_KEY
minio-secret-key-CHANGE-ME
Environment variable MINIO_ROOT_PASSWORD
region
us-west-2
This parameter is invalid in MinIO and can be set to any value, such as us-west-2.
endpoint
http://10.1.0.240:9000
The endpoint can be obtained by running the command sudo systemctl status minio.service.
data-bucket
automq-data
Set the bucket for storing messages.
ops-bucket
automq-ops
Set the bucket for storing operational data.

Deploy AutoMQ

Please refer to the following documentation to deploy AutoMQ: