Apache Qpid Broker-J - Multi-Version AMQP Broker

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

## Bridge Legacy and Modern AMQP on a Single Broker

Running separate brokers for legacy AMQP 0-9-1 or 0-10 clients and newer AMQP 1.0 services adds operational overhead and failure points. Apache Qpid Broker-J eliminates that complexity by speaking the full range of AMQP versions - 1.0, 0-8, 0-9, 0-9-1, and 0-10 - on one server. This cloudimg image delivers the broker preinstalled, hardened, and answering connections within minutes of launch on any standard EC2 instance.

## Secure by Default - No Known Credentials

Unlike a stock Qpid Broker-J installation that ships a well-known guest account, this image contains no rendered broker configuration at all. The broker cannot start until first boot generates a unique administrator password for your instance and renders a hardened configuration around it. Every listener - plaintext AMQP, secure AMQP, and the management console - requires authentication. There is no guest account and no anonymous access.

Additional security measures include:

• Management console bound to loopback and published only through an nginx TLS reverse proxy with a per-instance certificate
• A separate per-instance keystore securing the AMQPS listener
• Generated credentials stored in a root-only file on the instance

## Ready to Use on AWS

This image runs on standard EC2 instances under systemd on a headless Java runtime. There is no manual unpacking, no configuration authoring, and no proxy wiring required. Open port 22 for SSH, 443 for the management console, and 5672/5671 for messaging in your security group, and you are operational. An m5.large is a comfortable default; size up for higher throughput or deeper queues.

## Web Management Console and REST API

The built-in web management console lets you:

• Create and inspect queues and exchanges
• Bind queues to exchanges
• Browse and move messages
• Manage users and access control
• Watch connections and sessions live

Everything the console does is also available through its REST API, so queue provisioning and monitoring can be automated from your own tooling or integrated into CI/CD pipelines.

## Key Use Cases

• Multi-version AMQP bridging: Integrate legacy AMQP 0-9-1 or 0-10 applications with newer AMQP 1.0 services without running two brokers.
• Java-native messaging: Run a broker on the same runtime as your applications with a management REST API for automated provisioning.
• Secure dev/test/staging infrastructure: Launch message infrastructure that is locked down by default rather than opened up after the fact.

## Evaluate Before You Commit

A 7-day free trial is available on this listing. Launch on a smaller instance type such as a t3.medium for low-cost evaluation. Retrieve the generated administrator password over SSH, sign in to the management console, create your first queue, and connect a client - all within minutes. When you are ready for production, scale to an m5.large or larger.

## 24/7 cloudimg Support

Our team provides 24/7 technical support by email and live chat covering deployment, TLS certificate replacement, queue and exchange design, client connectivity across AMQP versions, access control, and sizing guidance.

Apache Qpid and Qpid Broker-J are 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.