Skip to content
RabbitMQ Message Broker product logo
  • AWS· soonComing soon on Amazon Web Services
  • Azure· nextMicrosoft Azure is next on the roadmap
  • GCP· nextGoogle Cloud is next on the roadmap
Coming soon

RabbitMQ Message Broker

RabbitMQ 4.3.5 on Erlang/OTP 27 with the management, Prometheus, shovel and federation plugins enabled, nginx in front of the management UI and Webmin for the host. The guest account is never created, the Erlang cookie and admin credential are generated per instance before the broker opens a port, and the distribution ports are loopback-only.

Version
v4.3.5
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Community

What's installed

Every package and version on the image. Nothing else is installed.

  • RabbitMQ 4.3.5
  • Erlang/OTP 27.3.4
  • rabbitmqadmin 2.35.0
  • nginx 1.24.0
  • Webmin 2.660

Licensing — Open source (MPL-2.0), no licence key required

Deploy anywhere

RabbitMQ Message Broker on AWS.

Microsoft Azure and Google Cloud are next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS

    Amazon Web Services

    AMI · v4.3.5

    Coming soon

    AWS AMI ID

    ami-074fcc778b524fd97
    Released
    September 12, 2026
    Root volume
    gp3 · 20 GiB

    Instance types

    • t3a.medium
    • t3.medium
    • t3a.large
    • m6a.large

    Regions

    • us-east-1
    AWS launch steps

Getting started

From launch to signed in, step by step.

  1. Launch in us-east-1 with TCP 22, 80, 5672 and 8000 open (add 15672 for the UI on its native port); wait for the health checks.

  2. Open http://<instance-public-ip>/ and sign in with username admin and your EC2 Instance ID as the password, exactly as the console shows it (for example i-0123456789abcdef0).

  3. Applications connect at amqp://<instance-public-ip>:5672 with the same credentials. Webmin is on port 8000, same username and password.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_rabbitmq.sh or pass_webmin.sh; rabbitmq_status.sh prints versions, node name and endpoints (with sudo: users, vhosts, queues).

  5. rabbitmqadmin is installed for scripting. Prometheus metrics on 15692 are loopback-only; open them deliberately if you scrape.

Security posture

What this image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official repository or release, nothing is copied from any third-party image, and the finished image was scanned for third-party vendor strings before capture.

  • No usable credential ships in the image; passwords are set on your instance at first boot from EC2 instance metadata (IMDSv2) and the scripts that set them delete themselves afterwards.

  • SSH is key-only, root login over SSH is refused, and build-time SSH keys, shell history and logs were removed before imaging.

  • The guest account is never created: because nginx proxies from 127.0.0.1, RabbitMQ's loopback-only guest would otherwise be reachable from the internet through port 80, so the default user is seeded as admin with a per-instance password instead.

  • The Erlang distribution port (25672) and epmd (4369) are bound to loopback - with the cookie, a reachable distribution port is remote code execution - and the cookie itself is regenerated per instance.

  • Prometheus metrics (15692) are loopback-only so they are opened deliberately, not by default.

  • First boot is idempotent and scrubs the plaintext seed password once the credential is confirmed.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges in your security group.