Getting Started
MicroVM Studio starts AWS Lambda MicroVMs from workspaces you set up, and gives each one a terminal on your Mac.
What you need
- An AWS account in a region with Lambda MicroVMs. AWS lists them on the Lambda MicroVMs page.
- An AWS profile on this Mac, in
~/.aws/configor~/.aws/credentials. Settings can make one for IAM Identity Center.
Setting up
Until you save a workspace, the main window shows Get started: a short checklist. Each line is ticked once it's done, says what it's set to, and has a button that opens Settings on the right tab. Do them in any order, and come back to any of them later in Settings. Once a workspace is saved, the checklist is gone for good.
- Add an AWS profile. Add a Profile… opens Settings → General. In the AWS profile menu at the top, Add a Profile… saves a profile for IAM Identity Center and signs you in in your browser. Using access keys? Run
aws configurein Terminal, then choose Reload Profiles in the same menu. See Profiles and Regions. - Choose regions. Choose Regions… opens Settings → General. Only the profile's default region is listed at first. Choose the default region from the listed ones, and add another with the pop-up and Add: a region MicroVMs aren't known to run in is checked before it's added.
- Choose a default image. Choose an Image… opens Settings → Images. Choose the default image for new workspaces: one of your images, or the starter image, built with the defaults for the size you choose. New Image… has every value and the Dockerfile. See Images.
- New workspace. New Workspace… opens the workspace editor.
Optional, in Settings
- Network. Quick start needs nothing here: MicroVMs reach the internet through AWS's own connector, shown as Internet egress and marked Built-in. A VPC connector is for Advanced use and for persistent storage, and needs a VPC with a NAT gateway of your own. See Network Connectors.
- Storage. A file system on one of your VPC connectors, for a persistent
/workspace. See Persistent /workspace. - GitHub. Sign In to GitHub…, then Add Another GitHub Account… once one is signed in. See GitHub.
- General → New workspaces. How new workspaces sign in to Claude Code (a token, an Anthropic API key, or Amazon Bedrock) and to Codex (ChatGPT in the MicroVM, or an OpenAI API key). Each workspace can change them.
- General → Permissions. Check Permissions is a read-only check of what your AWS identity can do, with a minimal IAM policy to copy if something's missing.
The starter image
The starter image has git, tmux, gh, the AWS CLI, Node 22, Claude Code and Codex, and a user called dev. It's built once in your AWS account and takes about 5 minutes. Its size is 1 vCPU · 2 GB unless you choose another; see Images. Before you press Build, the sheet lists what it makes in AWS: an S3 bucket for the recipe, an IAM role for the build, and the image. Closing the sheet doesn't stop the build. Build or update it later in Settings → Images.
Any of your images in the region can be the default instead: the starter image is simply the quickest way to start.
Your first workspace
A workspace is a saved recipe for a MicroVM. Press + next to Workspaces in the main window, give it a name, check the profile, region and image, and choose Save: Quick start needs nothing more. Then press Launch on it: the MicroVM starts, setup runs, and the terminal connects.
Everything else is in Settings. General has the profile's regions, what new workspaces start with, the permission check and the guardrails; Network Connectors, Images and Storage have the profile's connectors, images and file systems. GitHub, Secrets and Terminal are the same for every profile.