Skip to content
Zabbix Monitoring Server 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

Zabbix Monitoring Server

Zabbix 7.4.14 - server, frontend and agent 2 - on a full LAMP stack with phpMyAdmin and Webmin. The server monitors itself from the first boot with all 360 stock templates loaded: no setup wizard, no database to configure. A home page with live status lights shows you when the stack is ready.

Version
v7.4.14
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.

  • Zabbix server 7.4.14
  • Zabbix frontend 7.4.14
  • Zabbix agent 2 7.4.14
  • Apache 2.4.58
  • PHP 8.3.6
  • MySQL 8.0.46
  • phpMyAdmin 5.2.3
  • Webmin 2.660

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

Deploy anywhere

Zabbix Monitoring Server 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 · v7.4.14

    Coming soon

    AWS AMI ID

    ami-05f3f17e2eb136bed
    Released
    September 12, 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 and 8000 open; wait about two minutes. Open 10051 only if remote agents will report to this server.

  2. Open http://<instance-public-ip>/zabbix/ 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. To monitor another machine, install the Zabbix agent there, point it at this server, and add the host under Data collection → Hosts.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_zabbix.sh, pass_mysql.sh or pass_webmin.sh; zabbix-status reports services, endpoints, health checks and your database summary.

  5. Logs: /var/log/zabbix/. Change the passwords from the Instance ID once you are in - it is visible to anyone with read access to your AWS account.

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 first-boot step is time-bounded so a slow service can never leave the instance half-configured.

  • First boot sets the Zabbix, MySQL root and Webmin passwords from the Instance ID, gives the internal Zabbix database account a fresh random password, regenerates the MySQL maintenance credential, and gives phpMyAdmin a cookie key and control-user password unique to your instance.

  • MySQL listens on 127.0.0.1 only; Apache runs with ServerTokens Prod and ServerSignature Off.

  • Port 10051 only needs opening if remote agents report to this server.

  • The Instance ID is visible to anyone with read access to your AWS account, so change the passwords once you are in.

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