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
  • Yandex Container Solution
    • Resource relationships
      • Overview
      • Platforms
      • vCPU performance levels
      • Hardware generations
      • Preemptible VMs
      • VM network interfaces
      • Software accelerated network
      • Live migration
      • Placement groups
      • Statuses
      • VM maintenance policies
      • Serial console
      • Resetting Windows VM passwords
    • Graphics processing units (GPUs)
    • GPU VM maintenance
    • Images
    • Dedicated host
    • Reserved instance pools
    • Encryption
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes
  1. Concepts
  2. Virtual machines
  3. VM maintenance policies

Compute maintenance policies

Written by
Yandex Cloud
Updated at February 10, 2026
View in Markdown

Compute Maintenance Policies provide the ability to report the planned impact on the user VM by the cloud infrastructure using the metadata service.

A planned impact means the occurrence of one of the following VM maintenance events:

  • TERMINATE_ON_HOST_MAINTENANCE: User VM restart is scheduled.
  • MIGRATE_ON_HOST_MAINTENANCE: Live migration of user VM to another host (server) is scheduled.

You can use these criteria to set the VM maintenance policy:

  • Maintenance policy type: maintenance_policy.
  • Maintenance grace period: maintenance_grace_period.

The following maintenance policy types are supported:

  • RESTART: When a maintenance event occurs, the TERMINATE_ON_HOST_MAINTENANCE line appears in the metadata. After the maintenance_grace_period ends, the VM will be migrated to another host using the VM stop and run procedures.
  • MIGRATE: When a maintenance event occurs, the MIGRATE_ON_HOST_MAINTENANCE line appears in the VM metadata. After the maintenance_grace_period ends, the VM will be migrated to another host using the live migration procedure.
  • MAINTENANCE_POLICY_UNSPECIFIED: No policy is specified. Nothing is supplied to the metadata service; there is no wait time before maintenance.

When setting the maintenance grace period, keep in mind that you can delay the start of maintenance by the following maximum period after the maintenance event occurs:

  • Up to one minute for VMs without GPUs.
  • Up to 24 hours for VMs with GPUs.

Features for preemptible VMsFeatures for preemptible VMs

When maintenance events occur, preemptible VMs simply stop instead of migrating. No maintenance events appear in the VM metadata in this case.

Features for VMs with GPUsFeatures for VMs with GPUs

If the RESTART policy is set for VMs with GPUs (non-preemptible), email notifications about scheduled maintenance works on such VMs are disabled. During scheduled works, the VM will automatically restart following a maintenance_grace_period after a maintenance event appears in the metadata.

How to enableHow to enable

You can enable and configure VM maintenance policies using the CLI and Terraform. Currently you cannot configure maintenance policies from the management console.

LimitationsLimitations

A maintenance event can only be generated in the case of planned impact on a VM. If a VM fails, it may be restarted on another physical host. In this case, nothing appears in the VM metadata service. You will receive a failure notification by email.

Was the article helpful?

Previous
Statuses
Next
Serial console
© 2026 Direct Cursus Technology L.L.C.