Skip to content
Matomo Analytics 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

Matomo Analytics

Matomo 5.13.0 web analytics on a full LAMP stack with phpMyAdmin and Webmin - own your visitor data on your own instance. Apache serves Matomo directly, the archiver runs from cron as Matomo recommends, and a small service keeps trusted hosts and the site URL correct if your public IP changes, backing off the moment you set a real domain.

Version
v5.13.0
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.

  • Matomo 5.13.0
  • Apache 2.4.58
  • PHP 8.3.6
  • MySQL 8.0.46
  • phpMyAdmin 5.2.3
  • Webmin 2.660

Licensing — Open source (GPL-3.0), no licence key required

Deploy anywhere

Matomo Analytics 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 · v5.13.0

    Coming soon

    AWS AMI ID

    ami-0260416de664fa10b
    Released
    September 12, 2026
    Root volume
    gp3 · 30 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; wait two to three minutes.

  2. Open http://<instance-public-ip>/ and sign in with username admin. 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 website under Administration → Websites and paste the tracking code. The archiver runs every 15 minutes; real-time reports update immediately.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_matomo.sh, pass_mysql.sh or pass_webmin.sh; matomo_status.sh shows the stack at a glance.

  5. Once you have a domain and certificate, add force_ssl = 1 under [General] in /var/www/html/matomo/config/config.ini.php.

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.

  • Every credential and key is derived per instance at first boot: the Matomo admin, MySQL root and Webmin passwords, a fresh Matomo salt, and a fresh 32-byte phpMyAdmin cookie key.

  • Matomo connects to MySQL as its own dedicated user rather than root, so changing the root password never takes the site down.

  • MySQL listens on 127.0.0.1 only; phpMyAdmin's libraries and templates directories are denied over HTTP.

  • Matomo's System Check reports a single expected warning, Forced SSL, because the image is reached over HTTP at an IP address - enable it once you have a certificate.

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