Skip to main content
Basic VMs boot from a system-managed local SSD sized by the flavor. The create call attaches existing ports by ID, and the region is a field in the request body.
An API token is required, along with a project ID and a pre-created port in the target region.
REGION_ID is the numeric ID of a region that supports Basic VMs. Query the regions API and filter for regions where has_basic_vm is true.

Step 1. Select an image

Only Linux images are accepted. Query the images endpoint for the target region and save the ID of the chosen image.

Step 2. List Basic VM flavors

Basic VM flavors use the g1s-shared-* or g2s-shared-* naming scheme. Query the standard flavors endpoint and filter by name prefix.
The API returns:
The number after the RAM value in the flavor name is the local SSD size in GiB. Set FLAVOR_NAME to the chosen flavor.

Step 3. Create the Basic VM

Pass region_id in the request body. The boot disk is created with the flavor, and the request does not accept volume fields.
The API returns:
Poll GET /cloud/v1/tasks/{task_id} every 5 seconds until state is FINISHED, then read the instance ID from created_resources.
When complete:

Step 4. Get Basic VM details

The response includes boot_volume_id for the system-managed local disk. That disk is destroyed together with the VM on delete.
The API returns:

Step 5. Update the Basic VM

Rename the VM or replace its interface list. Updating interfaces[] replaces the whole list, and the interface order stays as it was at creation.
The API returns:
Poll the task until state is FINISHED.

Step 6. Delete the Basic VM

Deleting a Basic VM also destroys its system-managed boot disk. Ports attached to the VM are detached and are not deleted.
The API returns:
Poll the task until state is FINISHED.