Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
© 2025 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
  • Yandex Container Solution
    • Resource relationships
    • Graphics processing units (GPUs)
    • Images
      • Overview
      • Access
      • YAML specification
      • Instance template
      • Variables in an instance template
      • 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
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • Stopping a group
  • Pausing processes
  1. Concepts
  2. Instance groups
  3. Stopping and pausing an instance group

Stopping and pausing an instance group

Written by
Yandex Cloud
Updated at November 27, 2025
  • Stopping a group
  • Pausing processes

You can completely or partially stop an instance group.

Stopping a groupStopping a group

Completely stopping a group stops all the instances and interrupts the following processes: group autoscaling, automatic recovery and updating of instances.

The group's status first changes to STOPPING and then to STOPPED. The statuses of all instances first change to STOPPING_INSTANCE and then to STOPPED. Afterwards, no other charges are incurred for VM use.

Any significant changes to a stopped group, such as re-sizing the group or re-configuring instances, are only applied after the group starts.

To stop a group, follow this guide.

Pausing processesPausing processes

Note

You cannot pause an instance group that is being deleted. Also, you cannot run any operations for paused instance groups.

Pausing a group's processes interrupts only the following processes: group autoscaling, automatic recovery and updating of instances. All instances running when processes are paused continue to run.

The group's status changes to PAUSED. The statuses of all the instances remain unchanged, and you will continue to be charged for their use.

Any significant changes to the group, such as re-sizing the group or re-configuring instances, will not be applied until processes are resumed.

To pause a group's processes, follow this guide.

Was the article helpful?

Previous
Handling a stateful workload
Next
Sequentially restarting and recreating instances in a group
© 2025 Direct Cursus Technology L.L.C.