El

ElasticMQ on Ubuntu 24.04

Azure Streaming & Messaging

ElasticMQ, a self hosted message queue with an Amazon SQS compatible interface, so code that talks to Amazon SQS runs against a local queue with no AWS account.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

ElasticMQ is an open source, in memory message queue that speaks the Amazon SQS API. Point the AWS CLI, boto3 or any AWS SDK at its endpoint and you get a fully local, SQS compatible queue with no AWS account, no network egress and no per message cost. Developers use it to run SQS backed applications on their laptop, in CI pipelines and in air gapped environments, and to write fast, deterministic integration tests against real queue semantics rather than mocks.

This image runs ElasticMQ as a self contained service so a working SQS endpoint answers the moment the instance boots. It suits local and CI development, integration and load testing, demos, and any workload that wants Amazon SQS behaviour without the Amazon SQS bill.

Why the cloudimg image

cloudimg delivers ElasticMQ hardened and fully patched, with the queue bound to loopback behind an nginx reverse proxy. The image is secure by default and carries no usable login: ElasticMQ ships with no authentication of any kind, so cloudimg puts an HTTP login in front of it and, on the first boot of every instance, a one shot service generates a random admin password unique to that instance and writes it to a file only the root user can read. The AWS SDK endpoint on its own port stays open for drop in client use and is meant to be restricted at the network layer. The base is fully patched with unattended security upgrades enabled, and every deployment is paired with a step by step deploy guide and backed by 24/7 cloudimg support.

Common uses

  • Local and CI development against Amazon SQS
  • Integration and load testing of queue workloads
  • Air gapped or offline SQS compatible queueing