Skip to content
Snipe-IT IT Asset Management product logo
  • AWSAvailable on Amazon Web Services
  • AzureAvailable on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Snipe-IT 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
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. 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

LicensingOpen source (AGPL-3.0), no licence key required

Deploy anywhere

Snipe-IT IT Asset Management on AWS and Azure.

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
    Available

    Amazon Web Services

    AMI · v8.7.2

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    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
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.03/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Available

    Microsoft Azure

    Compute Gallery image · v8.7.2

    Azure Compute Gallery image ID

    Selected for you when you create the VM from the Azure Marketplace listing.

    Released
    OS disk
    Premium_LRS · 30 GiB
    VM sizes
    • Standard_D2as_v7
    • Standard_D2as_v5
    • Standard_B2ms
    • Standard_D4as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Launch on Azure MarketplaceAzure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region 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 AWS 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.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22, 80 and 8000 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match. Wait about three minutes for first boot.

  2. Open http://<vm-public-ip>/ and sign in as admin. phpMyAdmin is at /phpmyadmin (username root) and Webmin on port 8000 (username admin or root).

  3. The password is your VM ID: in the Azure portal open the virtual machine, choose Properties and copy VM ID - a 36-character value such as 02aab8a4-74ef-476e-8182-f6d2ba4166a6, typed exactly as shown in lower case.

  4. SSH as ubuntu with your key. Change passwords with sudo bash ~/iscripts/pass_snipeit.sh, pass_mysql.sh or pass_webmin.sh.

Security posture

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

  • Clean-room build on Canonical's official Ubuntu image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • The Snipe-IT administrator, MySQL root and Webmin passwords are all set on first boot from your VM's own vmId, and the Laravel application key is regenerated per VM.

  • The pre-image cleanup proves the build's own credentials are rejected before capture, and first boot sets every password from the new VM's own vmId, read from Azure IMDS.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and cloud-init installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture.

  • Verified against Microsoft's documented Linux certification test cases on a VM deployed from this gallery version - 13 passed, 0 failures - with VM extension provisioning confirmed and every helper script executed rather than only reviewed.

  • Restrict port 22 to trusted IP ranges, and put the consoles behind HTTPS with your own certificate before exposing them to the internet.