Skip to content
Jitsi Meet Video Conferencing 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

Jitsi Meet Video Conferencing

Jitsi Meet 2.0.11146 with Jitsi Videobridge, Jicofo and Prosody from the official Jitsi repository, plus Webmin - your own video conferencing server. Configured as a secure domain: only you can start meetings, and anyone with the link can join. The one ProvenCloud image served over HTTPS, because browsers refuse camera and microphone access on plain HTTP.

Version
v2.0.11146
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.

  • Jitsi Meet 2.0.11146
  • Jitsi Videobridge 2.3-307
  • Jicofo 1.0-1189
  • Prosody 0.12.4
  • OpenJDK 17.0.20
  • certbot 2.9.0
  • Webmin 2.660

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

Deploy anywhere

Jitsi Meet Video Conferencing 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 · v2.0.11146

    Coming soon

    AWS AMI ID

    ami-09783eb8a8c0f1e84
    Released
    September 13, 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, 443 and 8000 open and UDP 10000 - without UDP 10000 participants can join but no audio or video flows. Wait for the health checks.

  2. Open https://<instance-public-ip> (note https). Your browser will warn about the self-signed certificate: choose Advanced, then Proceed.

  3. To start a meeting, type a room name and sign in with username admin and your EC2 Instance ID as the password, exactly as the console shows it (for example i-0123456789abcdef0). Anyone you share the link with joins without an account.

  4. Webmin is at http://<instance-public-ip>:8000 with the same credentials.

  5. Remove the certificate warning: point a DNS A record at the server, then sudo jitsi-set-domain your-domain.com installs a Let's Encrypt certificate and registers renewal. Add hosts with sudo prosodyctl register <name> meet.provencloud.internal '<password>'.

  6. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_jitsi.sh, pass_webmin.sh or pass_all.sh; jitsi-info prints URLs, credentials, service status and the media port.

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.

  • Configured for secure domain rather than Jitsi's default: only the admin account can start a meeting, so strangers who find the address cannot consume your bandwidth, while anyone with a link can join a meeting already running.

  • First boot regenerates the Prosody component passwords for the videobridge and Jicofo and generates a fresh self-signed certificate - without that every customer would share component passwords and present an identical certificate.

  • Port 80 redirects to 443 and also serves Let's Encrypt validation.

  • Webmin runs in plain HTTP mode on 8000 with per-instance passwords.

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

  • Restrict ports 22 and 8000 to trusted IP ranges in your security group.