How to Update a MicroVM
Last verified 16 Nov 2026
DigitalOcean MicroVMs are lightweight virtual machines that run a container image in an isolated kernel, pause automatically when idle, and resume on the next request with memory, files, and processes intact.
You can change the following settings on an existing DigitalOcean MicroVM without recreating it:
- Name
- Tags
- Idle timeout: How long the MicroVM is not active before it pauses.
- Project
- Insights telemetry: Whether Insights stores the MicroVM’s logs and traces.
You can update a MicroVM while it is running or paused. An update does not restart, pause, or resume it.
All other settings, including the image, size, region, networking, ports, environment variables, auto-resume, and outbound policy, are fixed at creation. To change them, create a new MicroVM. To add or remove a MicroVM’s URLs, see How to Send Requests to a MicroVM.
Prerequisites
- To change the name, tags, or idle timeout with the API, a personal access token with the
microvm:readandmicrovm:updatescopes. - To move a MicroVM with the API, a personal access token with the
project:updatescope.
Update a MicroVM Using the Control Panel
Go to the MicroVMs page, click the MicroVM’s name, then click the Settings tab.
To rename the MicroVM, click Edit in the Name row, enter the new name in MicroVM name, then click Save. Names can contain 1 to 63 lowercase letters, numbers, and hyphens, and must be unique among your team’s MicroVMs in the region.
To change the MicroVM’s tags, click Edit in the Tags row, add or remove tags under Manage tags, then click Save.
To change the idle timeout, click Edit in the Idle timeout row, choose a new duration, then click Save. The maximum depends on your plan and is shown under the field. A new idle timeout takes effect within about a minute.
To move the MicroVM to another project, click Edit in the Project row, select the project, then save. Moving a MicroVM requires permission to assign resources to the destination project.
To change which telemetry Insights stores, click Edit in the Insights row, then turn platform logs or traces on or off. The row shows tags such as Metrics Enabled and Logs Enabled for the signals Insights stores. For details, see How to Monitor a MicroVM.
Update a MicroVM Using the API
Send a PATCH request to /v2/microvms/<your-microvm-id> with the fields to change. Set at least one field:
curl -X PATCH \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
-d '{
"name": "example-renamed",
"tags": ["web", "production"],
"auto_pause": {"idle_timeout": "15m"}
}' \
"https://api.digitalocean.com/v2/microvms/<your-microvm-id>"The request accepts the following fields:
name: The new name.tags: The complete set of tags. It replaces the current tags. An empty list removes every tag.auto_pause.idle_timeout: The new idle timeout, such as30s,15m, or1h. It must be greater than zero and no larger than your team’s maximum.
A successful request returns HTTP 200 and the updated microvm object. The endpoint returns the following errors:
| Status | Meaning |
|---|---|
| 400 | The request sets no fields, sets a field that is fixed at creation, sets auto_pause without idle_timeout, has an invalid value, or the MicroVM is not running or paused. |
| 409 | Another MicroVM on your team in the same region already has the name. |
| 413 | The request body is larger than 64 KiB. |
| 503 | A dependency is temporarily unavailable. If only the tag update failed, the name and idle timeout changes were applied. Send the request again to apply the tags. |
Move a MicroVM to Another Project Using the API
Use the assign resources endpoint to assign the resource do:microvm:<your-microvm-id> to the project.
The PATCH endpoint cannot move a MicroVM to another project or change its Insights telemetry. To change Insights telemetry, use the Control Panel. doctl cannot update a MicroVM.