Skip to content
Metabase Business Intelligence 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

Metabase Business Intelligence

Metabase OSS 0.63.16 on Java 25 with MySQL 8.0 as its application database, behind Apache, with phpMyAdmin and Webmin - dashboards and ad-hoc questions for your team without a SaaS bill. The site URL follows your public IP with zero extra restarts, and only the credentials you actually type are rotated at first boot.

Version
v0.63.16
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.

  • Metabase OSS 0.63.16
  • OpenJDK 25.0.4
  • MySQL 8.0.46
  • Apache 2.4.58
  • PHP 8.3.6
  • phpMyAdmin 5.2.3
  • Webmin 2.660

Licensing — Metabase OSS (AGPL-3.0), no licence key required

Deploy anywhere

Metabase Business Intelligence 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 · v0.63.16

    Coming soon

    AWS AMI ID

    ami-05b9aba43f0304971
    Released
    September 15, 2026
    Root volume
    gp3 · 12 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 and 8000 open; allow two to three minutes. GET /api/health returning ok is the true readiness signal.

  2. Open http://<instance-public-ip>/admin and sign in with admin@example.com. phpMyAdmin: /phpmyadmin (username root). Webmin: port 8000 (username admin). The password for all three is your EC2 Instance ID (for example i-0123456789abcdef0).

  3. Add your own databases under Admin → Databases. MySQL on this instance is loopback-only, so connect to it as 127.0.0.1.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_metabase.sh (any user, via the API), pass_mysql.sh or pass_webmin.sh.

  5. Metabase 63 is not an LTS line (end of life 2026-11-01). Plan a refresh when 0.64 ships, or ask us for a build on the 58 LTS line.

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 Metabase jar is pinned to the announced v0.63.16 release with its sha256 verified, rather than a moving latest URL.

  • Only the three credentials you actually type - Metabase admin, MySQL root, Webmin - are rotated to the Instance ID at first boot; Metabase's internal application-database credential is never exposed and therefore never rotated, so first boot never has to reconfigure or restart Metabase.

  • Passwords are changed through Metabase's HTTP API rather than its database, because the credential schema moves between releases.

  • Metabase is loopback-only behind Apache; MySQL listens on 127.0.0.1.

  • Verified on a fresh instance including a stop/start and a MySQL-restart regression.

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