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
    • 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
    • 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
    • Encryption
    • Backups
    • Quotas and limits
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  1. Concepts
  2. Instance groups
  3. Access

Access

Written by
Yandex Cloud
Updated at April 18, 2025

By default, all operations in Instance Groups are performed under a service account.

Service accounts are special accounts that can be used by services and applications to work with other Yandex Cloud APIs on your behalf. For more information about service accounts and access management in Yandex Cloud, see the Yandex Identity and Access Management documentation.

Instance Groups use authorized keys of the service account to authorize in the APIs and perform operations on resources within the roles granted to this service account. For example, Instance Groups can use a service account to create, update, and delete VM instances.

An instance group may only have one service account created in the same folder as the group.

To enable a service account to create, modify, run, restart, stop, or delete VM instances in a group, you need to assign this service account the compute.editor role for the folder where you want to place your instance group.

If you want to integrate an instance group with a Yandex Network Load Balancer, you also need to assign the load-balancer.editor role to the service account.

To integrate an instance group with an L7 load balancer from Yandex Application Load Balancer, assign the alb.editor role to the service account.

For more information, see Integrating an instance group with Network Load Balancer or Application Load Balancer.

Note

You cannot delete a service account used to manage an instance group while it is linked to this group. First, update the service account in the instance group settings or delete the instance group and then delete the service account.

Use casesUse cases

  • Running an autoscaling instance group

See alsoSee also

  • Creating an instance group
  • Creating a service account
  • Creating a fixed-size instance group with a network load balancer
  • Creating a fixed-size instance group with an L7 load balancer

Was the article helpful?

Previous
Overview
Next
YAML specification
© 2025 Direct Cursus Technology L.L.C.