Apache ActiveMQ Classic Message Broker by cloudimg

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

Apache ActiveMQ Classic is a mature, widely deployed open-source message broker written in Java. It implements the Jakarta Messaging (JMS) API and speaks a broad set of wire protocols, so applications written in Java, Python, .NET, C++, Node.js and more can exchange messages reliably through a single broker. This image is built for DevOps engineers and platform teams running event-driven services on AWS who need a production-ready broker without hours of manual configuration.

This image delivers ActiveMQ Classic fully installed, configured and supervised by systemd, so a working broker and its web management console are available within minutes of launch.

This build removes the manual work that normally stands between launch and a production-ready broker:

• No shipped default password - Stock ActiveMQ Classic ships a well-known administrator credential for both console and broker. This image contains none. A one-shot first-boot service generates a password unique to your instance, applies it to the console realm and the broker authentication plugin, and proves the rotation worked before recording anything.
• Multi-protocol out of the box - OpenWire plus AMQP, STOMP and MQTT are enabled and verified during the build, so heterogeneous clients connect without editing broker XML.
• Independently resizable storage - The persistence store lives on a dedicated volume mounted by filesystem identifier, so storage grows without rebuilding the instance.
• Console served safely - The management console is bound to the loopback interface and fronted by a reverse proxy, so it is reachable on the standard web port without exposing the raw management listener.

• Amazon EBS - The persistence store sits on a dedicated Amazon EBS volume, so message storage can be resized live, snapshotted for backup, and encrypted at rest.
• Apache Camel and Spring Boot - ActiveMQ Classic integrates natively with Camel routes and with Spring Boot through the JMS starter, so message-driven services need no extra adapter.
• Amazon EC2 - Launch on your preferred instance family; the image runs on general-purpose, compute-optimized, or memory-optimized instances depending on your throughput requirements.

On first boot a one-shot service generates a fresh administrator password unique to that instance, writes it into the console realm and the broker authentication configuration, then verifies the result: the console must reject an unauthenticated request and the stock default credential, must accept the new one, and a message must round-trip through the broker under it. Only then are the credentials written to a root-only file. If any check fails the service records nothing and retries on the next boot, so the broker never starts with an unproven password.

Apache ActiveMQ Classic is installed from the official Apache binary distribution, checksum-verified, and run by a dedicated unprivileged service account under systemd. The broker exposes the native OpenWire connector along with AMQP, STOMP and MQTT. A reverse proxy serves the loopback-bound console on the standard web port, alongside an unauthenticated health endpoint for load balancer checks.

1. Launch the image on your chosen instance type.
2. Connect over SSH as the default login user for your operating system variant.
3. Retrieve the generated credentials from the root-only file.
4. Browse to the instance public address and sign in to the management console.
5. Point your messaging clients at the broker connector and start publishing.

For a detailed walkthrough covering security hardening, EBS volume expansion and network-of-brokers configuration, contact cloudimg support for the deployment guide.

• Order processing backbone - Publish order events to a durable queue while warehouse, billing and notification services consume them independently. Because the broker persists messages, a consumer that is briefly offline receives its backlog on reconnect.
• Microservices decoupling - Use durable queues and publish-subscribe topics to isolate service boundaries.
• Protocol bridging - Connect legacy JMS applications and modern MQTT or AMQP clients through a single broker.
• Telemetry buffering - Buffer data from field devices over lightweight protocols before downstream processing.
• Job distribution - Reliably distribute tasks across a pool of workers with message acknowledgment.

Launch the AMI and have a working broker in minutes. For architecture guidance, a deployment consultation, or help planning a network-of-brokers topology, reach out to cloudimg support via email or 24/7 live chat.