Uptime Kuma

Uptime Kuma Verified

Self-hosted monitoring for HTTP, TCP, ping and more

monitoringuptimestatus-page

Self-hosted monitoring for HTTP, TCP, ping and more

  • Automated testing before each release
  • HTTP, TCP, ping and DNS probes with public status pages
  • Built-in SQLite storage, one-click CloudFormation deploy

Deploy quick reference

Launch URLStack Outputs → ResolvedLaunchUrl
The instance's public IPStack Outputs → PublicIp
Admin console/ · The first visit walks you through two one-time steps: pick a database (keep the default SQLite unless you have a specific need), then create the admin account. There are no preset credentials.
See the full step-by-step guide in Deployment

Quick Deploy

Image pinned by verified digest
us-east-1
t3.small
30 GB

≈ $23/mo — Verified default in us-east-1: ~$15.2 t3.small + $4 for 20 GB root and 30 GB data gp3 + $3.65 public IPv4 per month. Data transfer, snapshots and CloudWatch usage are extra.

After you deploy

  1. The CloudFormation wizard opens with everything prefilled (stack "corenova-uptime-kuma-2-5-3") — review and click "Create stack".
  2. Wait until the stack status reaches CREATE_COMPLETE (about 10 minutes). Outputs are only visible after completion.
  3. Open the stack's Outputs tab — everything you need is there:
    • ResolvedLaunchUrlAccess URL — open this in your browser
    • PublicIpThe instance's public IP
    • PublicDnsNameThe instance's public DNS name
  4. Open the access URL in your browser — the app is ready to use.
  5. Admin consoleOpen your access URL followed by this path: /

    The first visit walks you through two one-time steps: pick a database (keep the default SQLite unless you have a specific need), then create the admin account. There are no preset credentials.

Good to know

  • Monitoring data is stored on a retained data volume (/app/data). It keeps billing after stack deletion; snapshot it, then delete the volume when no longer needed.

Next steps

  • Your data lives at /app/data inside the container, on an encrypted EBS volume. Find the instance by its ID in the EC2 console.
  • Back up before any changes: Upgrading and backups guide
  • To upgrade to a newer verified version: Version history

Deleting the stack terminates the host, but the data volume is retained and continues billing. Snapshot it first, then delete the retained volume manually when you no longer need it.

VersionsVerified AtVerifiedStatusAWS Tested
2.5.3Sep 9, 2026 VerifiedNew VersionAWS · referenced

Configuration

Container Port

3001

AWS Regions

us-east-1

Supported Architectures

x86_64

AMI

ami-025d99823a4caad37

Updates

2.5.3Sep 9, 2026 VerifiedNew Version

FAQ

  • CoreNova Launch verifies software and provides deployable artifacts; deployment runs in your own AWS account.
  • Verification status comes from the upstream Manifest — the site never guesses it.