Skip to content
Rocket.Chat Team Chat Server product logo
  • AWSAvailable on Amazon Web Services
  • Azure· soonComing soon on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Rocket.Chat Team Chat Server

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
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. 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

LicensingRocket.Chat Community (MIT), no licence key required

Deploy anywhere

Rocket.Chat Team Chat Server on AWS and Azure.

Google Cloud is 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
    Available

    Amazon Web Services

    AMI · v8.8.1

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    Released
    Root volume
    gp3 · 20 GiB
    Instance types
    • t3a.medium
    • t3.medium
    • t3a.large
    • m6a.large
    Regions34 regions· show all
    • us-east-1
    • af-south-1
    • ap-east-1
    • ap-east-2
    • ap-northeast-1
    • ap-northeast-2
    • ap-northeast-3
    • ap-south-1
    • ap-south-2
    • ap-southeast-1
    • ap-southeast-2
    • ap-southeast-3
    • ap-southeast-4
    • ap-southeast-5
    • ap-southeast-6
    • ap-southeast-7
    • ca-central-1
    • ca-west-1
    • eu-central-1
    • eu-central-2
    • eu-north-1
    • eu-south-1
    • eu-south-2
    • eu-west-1
    • eu-west-2
    • eu-west-3
    • il-central-1
    • me-central-1
    • me-south-1
    • mx-central-1
    • sa-east-1
    • us-east-2
    • us-west-1
    • us-west-2
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.03/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Coming soon

    Microsoft Azure

    Compute Gallery image · v8.9

    Azure Compute Gallery image ID
    …/galleries/provencloud_marketplace/images/rocketchat/versions/2026.11.2
    Released
    OS disk
    Premium_LRS · 30 GiB
    Gallery
    provencloud_marketplace
    Definition
    rocketchat
    Resource group
    provencloud-marketplace-rg
    VM sizes
    • Standard_D2as_v7
    • Standard_D2as_v5
    • Standard_B2ms
    • Standard_D4as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Azure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region 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 AWS 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.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22, 80, 8081 and 8000 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match, and wait a few minutes for first boot to finish.

  2. Open http://<vm-public-ip>/ soon after the VM starts and complete the setup wizard to create your administrator account (whoever finishes it first becomes the admin, so keep port 80 limited to your own IP until you have done this). Mongo Express (port 8081) and Webmin (port 8000) sign in as admin with your VM ID (Azure portal > the virtual machine > Properties > VM ID, for example 02aab8a4-74ef-476e-8182-f6d2ba4166a6). Reset a chat password with sudo bash ~/iscripts/pass_rocketchat.sh.

  3. For production, limit admin ports to your own IP address.

Security posture

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

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • No two VMs share a login: first boot sets every password and secret key from the new VM's own vmId (read from Azure IMDS) or from fresh random values, and creates new SSH host keys.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and Azure installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture, and the image carries every Ubuntu 24.04 LTS security update with nothing pending.

  • Each gallery version is deployed as a Trusted Launch VM and checked against Microsoft's documented Linux certification test cases, the product's own end-to-end login tests and a stop/start cycle before it is published.

  • Restrict port 22 and the admin consoles to trusted IP ranges, and put public web consoles behind HTTPS with your own certificate.