Glossary
VM Image (AMI)
A frozen copy of a server’s disk that a cloud launches into as many identical machines as you like. The AWS name is AMI; every provider has an equivalent.
General definition
VM Image (AMI) describes a template copy of a virtual machine’s disk: the operating system, installed packages, application files and boot configuration, stored so that any number of identical servers can be launched from it. On AWS the format is the Amazon Machine Image (AMI); Azure calls it a VM image or, in its store, a VM offer; DigitalOcean sells them as 1-Click Droplets; other providers have custom images, snapshots or boot scripts that build the same result when the machine starts.
An image is built once and launched many times, which gives it three useful properties:
- Repeatable: every instance starts from the same bytes, so a tested image behaves the same in staging and in production
- Fast: packages and container images are already on the disk, so first boot takes minutes rather than an hour of downloads
- Immutable: updates ship as a new image version rather than as in-place patching, which is why marketplaces ask vendors to rebake for each release and scan the result for vulnerabilities
What an image must not contain is anything specific to one customer: domain names, passwords, certificates, licence keys. Those are injected at launch, by cloud-init user data, by a template such as AWS CloudFormation or Azure Resource Manager, or by a first-boot setup page the buyer opens in a browser. Marketplace rules go further: no default passwords, no baked-in SSH keys, no vendor credentials, and a current security baseline at bake time. Tools such as Packer automate the bake so it can run for every release.
Images sit between two other packaging choices. A container image holds one process and its libraries and needs a host to run on; a VM image holds the whole host. A Helm chart or a Kubernetes operator assumes a cluster already exists. In practice a vendor’s VM image is often a minimal operating system with Docker and the vendor’s containers pre-pulled, so the same software runs identically whether you start from the image, from Docker Compose on your own host, or on Kubernetes. The image is a convenience for the first server; high availability across several servers still has to be designed.
In the Ethora ecosystem
Ethora Core’s AWS Marketplace AMI is built exactly this way: Ubuntu 24.04 with security updates, Docker, the public installer and every Ethora container image pre-pulled, plus a first-boot setup page. Launch the instance, point the four DNS records at it and open the setup page, which asks for a root domain and an admin e-mail, installs the stack in about five minutes with Let’s Encrypt certificates, and then switches itself off. A CloudFormation template does the same unattended, with the answers passed as stack parameters. The image holds no secrets and no passwords: the setup page is protected by the instance id, and AWS injects your own SSH key pair.
The same first-boot setup page is packaged as a VM offer for Azure and as 1-Click and app images for DigitalOcean, Vultr and Akamai, with those listings in progress. Later updates do not need a new image: the installer’s update script on the instance brings the containers forward to the current release line. The current list of channels and their status is on the Get Ethora page.