AMIs and machine images
Coming from another cloud?
▸AWS·Amazon Machine Images (AMIs)
Amazon Machine Images (AMIs)
- Managed via EC2 APIs, not Glance.
- Region-specific with cross-region copy.
- Marketplace AMIs may charge hourly fees.
- Includes block device mapping in AMI.
▸Azure·Compute Gallery image definitions and versions
Azure Compute Gallery image definitions and versions
- Organized in galleries with image definitions and versioned images (Microsoft.Compute/galleries/images/versions), more structured than flat Glance images.
- Supports global replication to regions with replicas (up to 100), ZRS storage, unlike OpenStack's store-only model.
- Sharing via RBAC, community galleries, or direct share; requires gallery setup vs simple OpenStack image sharing.
- New features like Trusted Launch only in Gallery, legacy managed images deprecated.
▸DigitalOcean·Images (Distributions, 1-Click Apps, Snapshots, Backups, Custom Images)
Images (Distributions, 1-Click Apps, Snapshots, Backups, Custom Images)
- DigitalOcean classifies images into specific types (snapshots, backups, applications/1-Click, distributions, custom) rather than OpenStack Glance’s more generalized image model with visibility/properties/metadata.
- Custom images are imported by providing a URL to a supported disk format (raw, qcow2, vhdx, vdi, vmdk) and have a documented max decompressed size (100 GB), which differs from typical OpenStack flows where images are uploaded directly to Glance and size limits are operator-defined.
- DigitalOcean image operations are through /v2/images in their API, not Glance (and images also include DigitalOcean-specific fields like kind values base/snapshot/backup/custom/admin).
- DigitalOcean's "applications" images (1-Click Apps/Marketplace style) are a first-class image type, whereas OpenStack commonly treats such preconfigured stacks as separate concerns (OpenTofu modules, Heat templates, app catalogs) rather than an image 'type'.
▸Google Cloud·Machine Images (full VM state capture)
OS images
- Public images shareable across projects (e.g. debian-cloud); OpenStack typically tenant-private.
- Image families point to latest version; no OpenStack equivalent.
- Custom images stored in Cloud Storage with licensing fees for premium OS.
▸Hetzner·Images
Images
- Includes system images (OS), user images (snapshots/backups).
- API /v1/images; create via server action create_image (type=snapshot/backup).
- Billed per GB/month; backups cost 20% of server price.
- No direct image upload; custom via ISO attach or rebuild.
AMIs and machine images
An AWS AMI (Amazon Machine Image) is a boot template for EC2. On Quake AI the same role is an image in the Images service (OpenStack Glance): a disk template with metadata (minimum disk, OS family) that Nova uses when it creates an instance.
Instance snapshots can also become bootable images when you capture a running disk for clone or golden-image workflows.
Mapping image vocabulary#
| Elsewhere | On Quake AI |
|---|---|
| AMI | Image |
| Azure managed image / gallery image | Image |
| GCP machine image | Image |
| Custom image upload | Glance image import (see create an image) |
| Golden image pipeline | Packer publish to Glance (see build a golden image) |
Images are project-scoped unless shared. Pick an image that matches your workload OS and boot mode requirements before you select a flavor.
What to read next#
- Images: catalog, custom images, and visibility
- Flavors: CPU, RAM, and root disk pairing with images
- Instance snapshots: capture instance disk state into an image
Quick answers
Related content
Pages
How-tos
How to back up and restore a Quake AI VM
Compute
How to boot a virtual machine from an ISO image
Compute
How to build a golden VM image with Packer
Compute
How to configure a VM with cloud-init
Compute
How to create a virtual machine image
Compute
How to create an instance snapshot
Compute
How to customize a template's image and flavor
Automation
How to launch a Windows Server VM
Compute
How to patch and update a Quake AI VM
Compute
How to provision a production-ready VM
Compute
How to use a container registry with Quake AI
Kubernetes
Explanations
Reference
migration
Compute migration guides
Compute
How Quake AI uses OpenStack
Platform
Migrate from AWS EC2 to Quake AI compute
Compute
Migrate from Azure Virtual Machines to Quake AI Compute
Compute
Migrate from DigitalOcean Droplets to Quake AI Compute
Compute
Migrate from GCP Compute Engine to Quake AI compute
Compute
Migrate from Hetzner Cloud Servers to Quake AI Compute
Compute
Migrate from Linode compute instances to Quake AI compute
Compute
Migrate from Vultr to Quake AI compute
Compute
troubleshooting
evaluation