Skip to content
Rocket.Chat Team Messaging 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

Rocket.Chat Team Messaging

Rocket.Chat 8.8.1 with MongoDB 8.0 as a replica set, Mongo Express for a database console, nginx in front with websocket support, and Webmin - team chat on your own server. No administrator is pre-seeded: the first visit opens Rocket.Chat's setup wizard, and ROOT_URL is corrected before Rocket.Chat starts on every boot.

Version
v8.8.1
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.

  • Rocket.Chat 8.8.1
  • MongoDB 8.0.32
  • Node.js 22.22.3
  • Deno 2.3.1
  • Mongo Express 1.1.0
  • nginx 1.24.0
  • Webmin 2.660

Licensing — Rocket.Chat Community (MIT), no licence key required

Deploy anywhere

Rocket.Chat Team Messaging 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 · v8.8.1

    Coming soon

    AWS AMI ID

    ami-05fef99a560ca3497
    Released
    September 15, 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, 8000 and 8081 open; allow ten to fifteen minutes.

  2. Open http://<instance-public-ip>/ and complete Rocket.Chat's setup wizard to create the admin user and organisation.

  3. Mongo Express: port 8081. Webmin: port 8000. Both use username admin and your EC2 Instance ID as the password (for example i-0123456789abcdef0).

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_rocketchat.sh (works without the current password and signs out existing sessions), pass_mongoexpress.sh or pass_webmin.sh.

  5. A hostname you set under Administration → Site URL is detected and never overwritten by the IP sync. Logs: journalctl -u rocketchat -f.

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.

  • No Rocket.Chat administrator is pre-seeded - the database ships empty apart from the built-in bot with the setup wizard pending - so no shared admin credential can exist.

  • First boot sets the Mongo Express and Webmin passwords from the Instance ID and regenerates Mongo Express's cookie and session secrets, so no two instances share session-signing keys.

  • Rocket.Chat (3000) and MongoDB (27017) are bound to 127.0.0.1; only 22, 80, 8000 and 8081 are served.

  • The 7.x kernel packages are purged so an unattended upgrade cannot move the instance onto a kernel MongoDB will not run on.

  • 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.