Skip to main content
Tigris is a globally distributed, multi-cloud object storage service with built-in support for the S3 API. It uses Dynamic Data Placement and Access-Based Rebalancing to deliver low-latency access worldwide — without the need to manage replication or caching. When paired with Tigris, AutoMQ can run as fully stateless brokers, leveraging Tigris’s unique architecture to eliminate attached disks and replication overhead.

​
Quick Start with Docker Compose:

The easiest way to run AutoMQ with Tigris is using Docker Compose. This guide will walk you through setting up a single-node AutoMQ cluster backed by Tigris storage.

​
Prerequisites

​
Create Buckets in Tigris

AutoMQ requires two buckets: one for data storage and one for cluster’s metrics and logs. You can create them via the Tigris console or using the AWS CLI: 

# Configure credentials
export AWS_ACCESS_KEY_ID=YOUR_TIGRIS_ACCESS_KEY
export AWS_SECRET_ACCESS_KEY=YOUR_TIGRIS_SECRET_KEY
export AWS_ENDPOINT_URL_S3=https://t3.storage.dev

# Create buckets for AutoMQ data and operations storage
aws s3api create-bucket --bucket your-automq-data --endpoint-url https://t3.storage.dev
aws s3api create-bucket --bucket your-automq-ops --endpoint-url https://t3.storage.dev
Note : Bucket names must be globally unique across all Tigris users.

​
Configure Docker Compose

Edit the docker-compose.yaml file and update the Tigris credentials and bucket names: 

services:
  server1:
    container_name: "automq-server1"
    image: automqinc/automq:1.6.0-rc0
    stop_grace_period: 1m
    environment:
      # Replace with your Tigris credentials
      - KAFKA_S3_ACCESS_KEY=tid_YOUR_ACCESS_KEY_HERE
      - KAFKA_S3_SECRET_KEY=tsec_YOUR_SECRET_KEY_HERE
      - KAFKA_HEAP_OPTS=-Xms1g -Xmx4g -XX:MetaspaceSize=96m
        -XX:MaxDirectMemorySize=1G
      - CLUSTER_ID=3D4fXN-yS1-vsQ8aJ_q4Mg
    command:
      - bash
      - -c
      - |
        /opt/automq/kafka/bin/kafka-server-start.sh \
        /opt/automq/kafka/config/kraft/server.properties \
        --override cluster.id=$$CLUSTER_ID \
        --override node.id=0 \
        --override controller.quorum.voters=0@server1:9093 \
        --override controller.quorum.bootstrap.servers=server1:9093 \
        --override advertised.listeners=PLAINTEXT://server1:9092 \
        --override s3.data.buckets='0@s3://your-automq-data?region=auto&endpoint=https://t3.storage.dev' \
        --override s3.ops.buckets='1@s3://your-automq-ops?region=auto&endpoint=https://t3.storage.dev' \
        --override s3.wal.path='0@s3://your-automq-data?region=auto&endpoint=https://t3.storage.dev'
    networks:
      - automq_net

networks:
  automq_net:
    driver: bridge
Key Configuration Parameters:
  • KAFKA_S3_ACCESS_KEY - Your Tigris Access Key (starts with tid_)
  • KAFKA_S3_SECRET_KEY - Your Tigris Secret Key (starts with tsec_)
  • s3.data.buckets - Your data bucket name in the S3 URL (stores Kafka data)
  • s3.ops.buckets - Your ops bucket name in the S3 URL (stores operational metadata)
  • s3.wal.path - Write-Ahead Log path (typically same as data bucket)
  • endpoint=https://t3.storage.dev - Tigris S3-compatible endpoint
  • region=auto - Tigris automatically routes to the nearest region
For detailed information on these Tigris and S3 configuration parameters, refer to the AutoMQ Broker and Controller Configuration guide.

​
4. Start AutoMQ

Start the AutoMQ cluster with Docker Compose: 
docker-compose up -d
Check the logs to verify AutoMQ is running: 

docker-compose logs -f
You should see messages indicating:
  • Readiness check pass! (ObjectStorageReadinessCheck) - Connected to Tigris
  • The broker has been unfenced - Broker is ready
  • Kafka Server started - AutoMQ is running

​
Create a Topic

Create a Kafka topic using the AutoMQ CLI: 

docker run --network automq_net automqinc/automq:1.6.0-rc0 \
  /bin/bash -c "/opt/automq/kafka/bin/kafka-topics.sh \
  --create \
  --topic my-test-topic \
  --bootstrap-server server1:9092 \
  --partitions 3 \
  --replication-factor 1"
List all topics to verify: 

docker run --network automq_net automqinc/automq:1.6.0-rc0 \
  /bin/bash -c "/opt/automq/kafka/bin/kafka-topics.sh \
  --list \
  --bootstrap-server server1:9092"
Describe the topic: 

docker run --network automq_net automqinc/automq:1.6.0-rc0 \
  /bin/bash -c "/opt/automq/kafka/bin/kafka-topics.sh \
  --describe \
  --topic my-test-topic \
  --bootstrap-server server1:9092"

​
Produce and Consume Messages

Produce test messages: 

docker run --network automq_net automqinc/automq:1.6.0-rc0 \
  /bin/bash -c "/opt/automq/kafka/bin/kafka-producer-perf-test.sh \
  --topic my-test-topic \
  --num-records=10000 \
  --throughput 1000 \
  --record-size 1024 \
  --producer-props bootstrap.servers=server1:9092"
Consume messages: 

docker run --network automq_net automqinc/automq:1.6.0-rc0 \
  /bin/bash -c "/opt/automq/kafka/bin/kafka-console-consumer.sh \
  --topic my-test-topic \
  --bootstrap-server server1:9092 \
  --from-beginning \
  --max-messages 10"

​
Congratulations! 🎉

You’ve successfully deployed AutoMQ with Tigris as the storage backend! In this guide, you:
  • Created Tigris buckets for data and operational storage
  • Configured and launched a single-node AutoMQ cluster using Docker Compose
  • Connected AutoMQ to Tigris using S3-compatible endpoints
  • Created a Kafka topic with multiple partitions
  • Produced and consumed messages through AutoMQ
Your AutoMQ cluster is now running entirely stateless with all data durably stored in Tigris object storage. You can scale brokers up or down without worrying about data migration, and benefit from Tigris’ global distribution and zero egress fees.

​
Learn More

​
Tigris Resources