Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
  • Yandex Container Solution
    • Resource relationships
      • Overview
      • Platforms
      • vCPU performance levels
      • Preemptible VMs
      • VM network interfaces
      • Software-accelerated network
      • Live migration
      • Placement groups
      • Statuses
      • VM maintenance policies
      • Resetting Windows VM passwords
    • Graphics processing units (GPUs)
    • Images
    • Dedicated host
    • Encryption
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • VMs as a Yandex Cloud resource
  • Availability zone
  • Computing resources
  • Disks
  • Statuses
  • Metadata
  • Network
  • Use cases
  1. Concepts
  2. Virtual machines
  3. Overview

VMs in Compute Cloud

Written by
Yandex Cloud
Improved by
Danila N.
Updated at June 3, 2025
  • VMs as a Yandex Cloud resource
  • Availability zone
  • Computing resources
  • Disks
  • Statuses
  • Metadata
  • Network
  • Use cases

A virtual machine is similar to a server in cloud infrastructures.

VMs as a Yandex Cloud resourceVMs as a Yandex Cloud resource

A VM is created in a folder within your cloud and inherits access rights from it. You can read more about the Yandex Cloud resource hierarchy here.

Each VM has a unique ID and name. The name is unique within the folder. Follow these naming requirements:

  • It must be from 2 to 63 characters long.
  • It can only contain lowercase Latin letters, numbers, and hyphens.
  • It must start with a letter and cannot end with a hyphen.

Note

The VM name is used to generate an internal FQDN, which is set only once, when you create the VM. If the internal FQDN is important to you, make sure to choose an appropriate name for your VM.

The ID is generated automatically when the VM is being created and is unique within Yandex Cloud.

You can move a VM to another folder within a single cloud.

Availability zoneAvailability zone

When creating a VM, you can select a Yandex Cloud availability zone to place it in.

To move a VM to a different availability zone, use a special CLI command or create a VM copy in the destination availability zone and then delete the source VM.

Computing resourcesComputing resources

When creating a VM, you need to specify the amount of computing resources to allocate to it; this includes the number and performance of processor cores (vCPUs) and the amount of RAM. You can choose the computing resources that are appropriate for the expected load. For more information, see vCPU performance levels.

DisksDisks

A VM must have at least one disk attached, which is a boot disk. Currently, you can only attach a boot disk when creating a VM.

You can also attach additional disks to your VM. You can either attach a previously created disk or create one with a new VM. You can create an empty disk or restore it from a snapshot or an image.

Note

Empty disks do not have a file system. If you are attaching an empty disk, partition and mount it manually. Alternatively, rather than attaching an empty disk, you can create a snapshot of the boot disk and use it to create a VM.

You can attach and detach additional disks even after you created the VM.

Read more about disks in Disks.

StatusesStatuses

The status of a VM determines which operations you can currently perform on it.

For example, the STOPPED status means the VM is stopped and you cannot connect to it. To connect to such a VM, you must start it first. After the status changes to RUNNING and the OS boots, you will be able to connect to the VM.

For more information about statuses, see VM statuses.

MetadataMetadata

You can specify your own metadata when creating or updating VMs. For example, to connect to a Linux VM, you need to provide an SSH key to it. which can be done using the metadata service. For more information, see VM metadata.

NetworkNetwork

When creating a VM, you need to specify its network interface settings by selecting the subnet to connect the VM to, configuring an internal and public IP address, and adding the required security groups. This will allow the VM to work with other services on the intranet and internet.

For more information, see VM network interfaces.

Use casesUse cases

  • Scheduled instance group scaling
  • Configuring a secure GRE tunnel over IPsec
  • Configuring time synchronization using NTP
  • Transferring logs from a VM to Yandex Cloud Logging
  • Assigning a domain name to a web server VM

Was the article helpful?

Previous
Resource relationships
Next
Platforms
© 2025 Direct Cursus Technology L.L.C.