Images

A MicroVM runs from an image built in your AWS account. The image decides what's installed, and the MicroVM's size and architecture. Settings → Images lists the images in a profile and region, builds new ones and updates them.

The list

The tab is for the profile Settings shows (the switcher at the top). Choose the region from the profile's listed regions.

New Image…

New Image… opens a sheet with two views, Quick start and Advanced, the way the workspace editor does.

Quick start images

A name, a region and a size. Everything else takes the default: ARM64, git, GitHub CLI, tmux, Node.js 22, Python 3, the AWS CLI, Claude Code, Codex and the EFS tools, all OS capabilities, and the mount at launch. It keeps the EFS tools and the mount, so a quick start image still works if you turn on persistent storage later.

Advanced images

Every value, with everything it offers shown:

Before Build, the sheet lists what it creates, with their tags: the S3 bucket and the recipe in it, the IAM role for the build and its policies, and the image. AWS writes the build's log to CloudWatch. Closing the sheet doesn't stop the build.

The Dockerfile

The last section of Advanced shows the Dockerfile the build uploads. While you only use the choices above it, the file is written from them and changes as they do. Type in it and it becomes yours: the build uploads exactly your text, and the choices that write it (packages, extra setup, mount at launch) lock. Reset to Generated goes back to the file the choices write.

The file must not be empty, must start with FROM (comments and blank lines may come first), and must fit the size the build upload allows; the sheet says in plain words what's wrong. What you control and what the build call keeps lists the rules:

Sizes

An image's size sets the vCPUs and memory of every MicroVM made from it, and so what it costs: CPU follows memory. These are the five sizes, with their compute price an hour while running in us-east-1; the sheet shows the price in the image's own region.

The starter image is 1 vCPU · 2 GB unless you choose another. Your AWS account's memory quota counts each MicroVM's size, per architecture: see Memory quota reached in Troubleshooting.

An image with Claude Code or Codex keeps them in its MicroVMs' memory, because a MicroVM reads its disk slowly the first time: they start in a second or two instead of 12 to 35. That takes about 330 MB of the MicroVM's memory for each, which nothing else can use. To give it back, add : > /etc/microvm-studio/keep-in-memory to the image's extra setup.

Persistent /workspace in an image

Both are on in the starter image and in Quick start images. The row of an image MicroVM Studio built says when one is missing.

Update…

Update… opens the recipe of an image MicroVM Studio built. Change it, then Update builds a new version under the same name and region; a new name or region would make another image. If nothing changed, the image is already up to date. AWS keeps only a hash of the extra setup, so if this Mac doesn't have it, type it again, or leave it empty to build without it.

Delete…

Delete… deletes the image and all its versions in its region. MicroVMs already running from it keep running, and it can't be undone. An image a saved workspace uses can't be deleted: choose another image for the workspace first. Deleting the default image for new workspaces leaves no default. AWS base images can't be deleted.