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
    • Graphics processing units (GPUs)
    • GPU VM maintenance
    • Images
      • Overview
      • Temporarily disabling availability zones
      • Access
      • YAML specification
      • Instance template
      • Variables in an instance template
        • Overview
        • Allocation policy
        • Deployment policy
        • Scaling policy
        • Recovery policy
      • Scaling types
      • Instance health checks and automatic recovery
      • Integrating with network and L7 load balancers
      • Handling a stateful workload
      • Stopping and pausing an instance group
      • Sequentially restarting and recreating instances in a group
      • Statuses
    • 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. Instance groups
  3. Policies
  4. Recovery policy

Recovery policy

Written by
Yandex Cloud
Updated at July 9, 2026
View in Markdown

When creating an instance group, you can choose how instances that fail a health check or an application health check will be recovered.

You can set the recovery policy in the auto_healing_policy key in the YAML file.

You can manage recovery policies using the CLI.

Here is how a YAML file entry may look like:

...
auto_healing_policy:
  auto_healing_action: RESTART
...

Where:

Key Value
auto_healing_action Instance recovery action. There are three types of actions:
  • RESTART: On failure, the instance will be restarted.
  • RECREATE: On failure, the original instance will be deleted with a new one deployed in its place.
    Recreation may be helpful if the data is irrelevant, and the software needs to be redeployed.
  • NONE: Disables recovery for the group's instances.
    Use if you need to recover the instance manually or retrieve its data for diagnostics.
The default value is RESTART.

If you do not set the recovery policy, the VM instances will be auto-healed depending on the deployment policy settings.

Useful linksUseful links

  • Scaling policy
  • Allocation policy
  • Deployment policy

Was the article helpful?

Previous
Scaling policy
Next
Scaling types
© 2026 Direct Cursus Technology L.L.C.