a self-hosted, Amazon SQS-compatible message queue for local development, CI and testing
ElasticMQ is an open source message queue that speaks the Amazon SQS REST API. Point aws-cli, boto3 or any AWS SDK at it with a single endpoint override and you get a local, self-hosted SQS with no AWS account, no network egress and no per-message charges. It is the standard choice for local development, CI and integration testing, demos and lightweight self-hosted queueing.
The cloudimg image ships ElasticMQ hardened for AWS: the queue engine is bound to loopback and fronted by nginx, exposing an unauthenticated drop-in SQS port for SDK clients and a per-instance Basic Auth gated management port, so the queue is never left world-open by accident. A per-instance admin password is generated on first boot, the Apache 2.0 licence is baked in, and every image is backed by 24/7 cloudimg support.
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
## Overview
ElasticMQ is an open source message queue with a fully Amazon SQS-compatible REST interface. Point aws-cli, boto3, the AWS SDKs or Spring Cloud AWS at ElasticMQ with a single endpoint override and you get a local, self-hosted SQS - no AWS account, no network egress, and no per-message charges. It is the standard choice for local development, CI and integration testing, demos, and lightweight self-hosted queueing where a full managed queue service is unnecessary. This AMI delivers ElasticMQ fully installed and hardened on AWS so you have a working SQS-compatible endpoint within minutes of launch - no JVM setup, no reverse-proxy configuration, and no credential wiring required.
## What Is Included
## Why This AMI Over a Manual Install
Running ElasticMQ safely for a team means more than downloading a jar: you need a service account, a systemd unit, a reverse proxy that separates the unauthenticated SDK endpoint from an authenticated management endpoint, a per-host credential, and a health check. This image does all of that. Because ElasticMQ has no authentication of its own, this appliance binds the queue engine to localhost and fronts it with nginx, so the queue is never left as a world-open unauthenticated service by accident.
## Security Practices
## Storage - In Memory by Design
ElasticMQ runs with in-memory storage, which is its canonical mode for development, CI and testing. Queues and messages are held in memory and are lost on service restart or instance reboot. This is intentional and documented on the instance MOTD, in the credentials file, and in the user guide. If you need durable queues, ElasticMQ supports optional file and embedded-database persistence that you can enable in the configuration - the user guide explains how.
## Use Cases
## Getting Started
Launch the AMI, SSH in as the login user for your operating system variant, and read your unique admin password from /root/elasticmq-credentials.txt. Point any SQS client at the drop-in endpoint with an endpoint-url override and dummy AWS credentials. For a guided setup or a durability/persistence review, contact cloudimg support.
## About ElasticMQ
ElasticMQ is an open source project by SoftwareMill, distributed under the Apache License 2.0.
All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.