Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
    • All guides
        • Stopping and starting a VM
        • Resetting a Windows Server VM user password
        • Attaching a disk to a VM
        • Detaching a disk from a VM
        • Moving a VM to a different availability zone
        • Moving a VM to a different folder
        • Moving a VM to a different cloud
        • Updating a VM
        • Changing VM computing resources
        • VM maintenance policy management
        • Configuring VM access permissions
        • Linking a service account to a VM
        • Deleting a VM
    • Viewing operations with resources
    • Viewing metrics Monitoring
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes

In this article:

  • Stopping
  • Starting
  • Restarting
  1. Step-by-step guides
  2. VMs
  3. Management
  4. Stopping and starting a VM

Stopping, starting, or restarting a VM

Written by
Yandex Cloud
Updated at July 31, 2026
View in Markdown
  • Stopping
  • Starting
  • Restarting

StoppingStopping

The Stop command shuts down a VM. Once a VM is shut down, its status changes to Stopped. While the VM is stopped, you will not be charged for it. Disk usage is billed separately, regardless of the VM's state.

You can restart a VM at any time to continue using it. All your data and changes will be saved.

Certain VM parameters can only be modified when the VM is stopped.

To stop a VM:

Management console
CLI
API
  1. In the management console, select the folder this VM belongs to.
  2. Navigate to Compute Cloud.
  3. To stop a single VM, select the VM, click , and select Stop.
  4. In the window that opens, click Stop.

To stop multiple VMs, select the VMs from the list, click Stop at the bottom of the screen, and then, in the window that opens, click Stop.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

  1. See the description of the CLI command for stopping a VM:

    yc compute instance stop --help
    
  2. Get a list of all VMs in the default folder:

    yc compute instance list
    

    Result:

    +----------------------+-----------------+---------------+---------+----------------------+
    |          ID          |       NAME      |    ZONE ID    | STATUS  |     DESCRIPTION      |
    +----------------------+-----------------+---------------+---------+----------------------+
    | fhm0b28lgfp4******** | first-instance  | ru-central1-a | RUNNING | my first vm via CLI  |
    | fhm9gk85nj7g******** | second-instance | ru-central1-a | RUNNING | my second vm via CLI |
    +----------------------+-----------------+---------------+---------+----------------------+
    
  3. Select ID or NAME of the VM, e.g., first-instance.

  4. Stop the VM:

    yc compute instance stop first-instance
    

Use the stop REST API method for the Instance resource or the InstanceService/Stop gRPC API call.

When a VM stops, the hypervisor sends a shutdown signal to the VM operating system. The OS has 30 seconds to gracefully terminate all running processes to avoid data loss. After this time elapses, the VM will be forcibly terminated.

StartingStarting

The Start command starts a previously stopped VM. Once the VM is started, its status changes to Running, and the operating system starts loading. From this point on, you start paying for using the VM.

To start a VM:

Management console
CLI
API
  1. In the management console, select the folder this VM belongs to.
  2. Navigate to Compute Cloud.
  3. To start a single VM, select the VM, click , and select Start.
  4. In the window that opens, click Start.

To start multiple VMs, select the VMs from the list, click Start at the bottom of the screen, and then, in the window that opens, click Start.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

  1. See the description of the CLI command for starting a VM:

    yc compute instance start --help
    
  2. Get a list of all VMs in the default folder:

    yc compute instance list
    

    Result:

    +----------------------+-----------------+---------------+---------+----------------------+
    |          ID          |       NAME      |    ZONE ID    | STATUS  |     DESCRIPTION      |
    +----------------------+-----------------+---------------+---------+----------------------+
    | fhm0b28lgfp4******** | first-instance  | ru-central1-a | RUNNING | my first vm via CLI  |
    | fhm9gk85nj7g******** | second-instance | ru-central1-a | RUNNING | my second vm via CLI |
    +----------------------+-----------------+---------------+---------+----------------------+
    
  3. Select ID or NAME of the VM, e.g., first-instance.

  4. Run the VM:

    yc compute instance start first-instance
    

Use the start REST API method for the Instance resource or the InstanceService/Start gRPC API call.

RestartingRestarting

The Restart command restarts a VM.

To restart a VM:

Management console
CLI
API
  1. In the management console, select the folder this VM belongs to.
  2. Navigate to Compute Cloud.
  3. To restart a single VM, select the VM, click , and select Restart.
  4. In the window that opens, click Restart.

To restart multiple VMs, select the VMs from the list, click Restart at the bottom of the screen, and then, in the window that opens, click Restart.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

  1. See the description of the CLI command for restarting a VM:

    yc compute instance restart --help
    
  2. Get a list of all VMs in the default folder:

    yc compute instance list
    

    Result:

    +----------------------+-----------------+---------------+---------+----------------------+
    |          ID          |       NAME      |    ZONE ID    | STATUS  |     DESCRIPTION      |
    +----------------------+-----------------+---------------+---------+----------------------+
    | fhm0b28lgfp4******** | first-instance  | ru-central1-a | RUNNING | my first vm via CLI  |
    | fhm9gk85nj7g******** | second-instance | ru-central1-a | RUNNING | my second vm via CLI |
    +----------------------+-----------------+---------------+---------+----------------------+
    
  3. Select ID or NAME of the VM, e.g., first-instance.

  4. Restart the VM:

    yc compute instance restart first-instance
    

Use the restart REST API method for the Instance resource or the InstanceService/Restart gRPC API call.

Was the article helpful?

Previous
Getting the serial port output
Next
Resetting a Windows Server VM user password
© 2026 Direct Cursus Technology L.L.C.