Skip to content
Uptime Kuma Monitoring Server product logo
  • AWS· soonComing soon on Amazon Web Services
  • Azure· soonComing soon on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Coming soon

Uptime Kuma Monitoring Server

Uptime Kuma 2.5.5 on Ubuntu 26.04 LTS: watch websites, APIs, TCP ports, ping targets, DNS records and page keywords, get alerts by email, Slack, Telegram, Discord, Microsoft Teams and many more, and publish status pages for your users. It runs in Docker with its embedded MariaDB, behind nginx over HTTPS, and every instance creates its own admin password and TLS certificate on first boot.

Version
v2.5.5
Operating system
Ubuntu 26.04 LTS
Architecture
x86_64
Support
Email support

What's installed

Every package and version on the image. Nothing else is installed.

  • Uptime Kuma 2.5.5
  • MariaDB 10.11.14 (embedded)
  • Node.js 22.22.3
  • nginx 1.28.3
  • Docker CE 29.9.3
  • Docker Compose 5.7.0
  • Ubuntu 26.04.1 LTS

LicensingOpen source (MIT), no licence key required

Deploy anywhere

Uptime Kuma Monitoring Server on AWS.

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

    Amazon Web Services

    AMI · v2.5.5

    Coming soon
    AWS AMI ID
    ami-070ae0104774d3d09
    Released
    Root volume
    gp3 · 30 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
    AWS launch steps

Getting started

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region with TCP 22, 80 and 443 open; wait two to three minutes for first boot.

  2. SSH as ubuntu with your key pair and run sudo pc-credentials show to read your admin password.

  3. Open https://<instance-public-ip>/ and sign in as admin. The certificate is self-signed for the instance's IP address, so your browser warns you the first time.

  4. Change the password under Settings > Security. If you lose it, run sudo docker exec -it uptime-kuma npm run reset-password.

  5. To use your own domain, replace /etc/ssl/certs/provencloud-uptime-kuma.crt and /etc/ssl/private/provencloud-uptime-kuma.key with your certificate and run sudo systemctl reload nginx.

  6. Monitoring data lives in /opt/uptime-kuma/data. Restrict port 22 to your own IP address in your security group.

Security posture

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

  • Clean-room build on Canonical's official Ubuntu 26.04 LTS image with every current security update applied; Docker comes from Docker's own repository and Uptime Kuma from its official 2.5.5 container image.

  • No password ships in the image.

  • On first boot each instance generates its own TLS certificate for its public IP and creates the Uptime Kuma admin account with a random password, stored root-only and read with sudo pc-credentials show; the password is handed to the application over standard input, never on a command line or in the console log. nginx will not start until that first-boot step has succeeded, so Uptime Kuma's setup page is never reachable from the network.

  • Uptime Kuma listens only on 127.0.0.1:3001; nginx serves it over HTTPS (TLS 1.2 and 1.3) with WebSocket support and redirects HTTP to HTTPS.

  • UFW allows only SSH, HTTP and HTTPS; fail2ban guards SSH; SSH accepts public keys only and refuses root.

  • Unattended security upgrades, auditd rules on accounts, SSH, nginx and the Uptime Kuma configuration, and AppArmor are enabled, and Docker logs rotate.

  • Build-time SSH keys, host keys, shell history, logs and all build data were removed before imaging.