Skip to content
Snipe-IT Asset Management 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

Snipe-IT Asset Management

Snipe-IT 8.7.2 IT asset management on Apache, PHP 8.3 and MySQL 8.0 with phpMyAdmin and Webmin. The setup wizard is already completed so you land on the login page, APP_URL follows your public IP across a stop/start, and every key and password - APP_KEY, OAuth keys, database and console passwords - is generated per instance.

Version
v8.7.2
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.

  • Snipe-IT 8.7.2
  • Apache 2.4.58
  • PHP 8.3.6
  • MySQL 8.0.46
  • phpMyAdmin 5.2.3
  • Webmin 2.660
  • Composer 2.10.3

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

Deploy anywhere

Snipe-IT Asset Management 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 · v8.7.2

    Coming soon

    AWS AMI ID

    ami-058daa8c5542aab34
    Released
    September 10, 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. Mail is set to log until you point MAIL_* in /var/www/html/snipeit/.env at real SMTP; until then password-reset mails land in storage/logs/laravel.log.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_snipeit.sh, pass_mysql.sh or pass_webmin.sh; snipeit_status.sh shows versions, endpoints, APP_URL and asset counts.

  5. Set your own domain as APP_URL and the IP sync leaves it alone. Upgrades use Snipe-IT's own php upgrade.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.

  • Nothing security-relevant is shared between two instances launched from this image: first boot generates its own Snipe-IT APP_KEY, Passport OAuth signing keys, database password, phpMyAdmin cookie key and control-user password, MySQL root and maintenance passwords, Webmin passwords, SSH host keys and machine-id.

  • Each password script proves the change with a real login before finishing.

  • MySQL is loopback-only; the MySQL root change goes through a socket-authenticated maintenance account, so no current password is needed for recovery.

  • Downloads were checksum- or signature-verified (phpMyAdmin sha256, Composer signature).

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