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
      • Creating a reserved instance pool
      • Updating a reserved instance pool
      • Deleting a reserved instance pool
      • Managing instances in a pool
    • Enabling a software-accelerated network
    • Viewing operations on service resources
    • Viewing metrics in Monitoring
    • NVIDIA driver update guide
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. Reserved instance pools
  3. Creating a reserved instance pool

Creating a reserved instance pool

Written by
Yandex Cloud
Improved by
Danila N.
Updated at July 20, 2026
View in Markdown

Warning

Reserved instance pools are billable: you pay for the whole unused volume of reserved computing resources of VMs, GPU clusters, and software accelerated networks according to the Yandex Compute Cloud pricing policy. For more information, see Using reserved instance pools.

The reserved instance pool feature is at the Preview stage.

To create a reserved instance pool:

Management console
CLI
API
  1. In the management console, select the folder you want to create a reserved instance pool in.

  2. Navigate to Compute Cloud.

  3. In the left-hand panel, select VM reserve pools.

  4. Click Create pool.

  5. Select the availability zone you want to reserve computing resources in.

  6. Select the pool type:

    • Standard: Number of linked VMs is limited by the pool size.
    • With oversubscription: You can link any number of VMs. The number of running VMs is limited by the pool size.
  7. Specify Pool size, which is the maximum number of VMs in the pool.

  8. Under VM computing resources, select one of the preset configurations or create a custom one. To create a custom configuration:

    • Go to the Custom tab.
    • Select a platform.
    • Specify the guaranteed performance and required number of vCPUs, as well as RAM size.
    • Enable a software accelerated network if needed.
  9. Under General information about the pool:

    • Enter a name for the pool. The naming requirements are as follows:

      • Length: between 3 and 63 characters.
      • It can only contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    • Optionally, add a description of the pool.

    • Optionally, add pool labels.

  10. Click Create.

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 Yandex Cloud CLI command for creating a reserved instance pool:

    yc compute reserved-instance-pool create --help
    
  2. Create a reserved instance pool in the default folder:

    yc compute reserved-instance-pool create \
      --name <pool_name> \
      --description <pool_description> \
      --zone-id <availability_zone_ID> \
      --size <pool_size> \
      --platform <platform_ID> \
      --cores <number_of_vCPUs> \
      --memory <RAM_amount> \
      --gpus <number_of_GPUs> \
      --gpu-cluster-id <GPU_cluster_ID> \
      --allow-oversubscription
    

    Where:

    • --name: Name of the new pool. The naming requirements are as follows:

      • Length: between 3 and 63 characters.
      • It can only contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    • --description: Description of the new pool. This is an optional setting.

    • --zone-id: ID of the availability zone to reserve computing resources in.

    • --size: Number of slots per pool. This is an optional setting. The default value is 0.

    • --platform: Platform where the computing resources are reserved. This is an optional setting. The default value is standard-v2 (Intel Cascade Lake).

    • --cores: Number of vCPUs for VMs in the new pool. This is an optional setting. The default value is 2.

    • --memory: Amount of RAM for VMs in the new pool. This is an optional setting. The default value is 2 GB.

    • --gpus: Number of GPUs for VMs in the new pool. This is an optional setting. This parameter is only available if you select a platform with GPU support.

    • --gpu-cluster-id: GPU cluster ID. This is an optional setting.

    • --allow-oversubscription: Parameter enabling the oversubscription mode for the pool. In this mode, you can attach stopped VMs in a quantity that exceeds the pool's capacity. This is an optional setting. The oversubscription mode is off by default.

    Result:

    done (8s)
    id: fv4vnl1ncbja********
    zone_id: ru-central1-a
    cloud_id: b1gia87mbaom********
    folder_id: b1gt6g8ht345********
    name: test-pool
    description: sample description
    created_at: "2025-08-12T07:58:57Z"
    platform_id: standard-v2
    resources_spec:
      memory: "2147483648"
      cores: "2"
      core_fraction: "100"
    gpu_settings: {}
    network_settings:
      type: STANDARD
    size: "2"
    committed_size: "2"
    slot_stats:
      total: "2"
      unavailable: "2"
    instance_stats: {}
    

    For more information about the yc compute reserved-instance-pool create command, see the Yandex Cloud CLI reference.

Use the create REST API method for the ReservedInstancePool resource or the ReservedInstancePoolService/Create gRPC API call.

Useful linksUseful links

  • Managing VMs in a reserved instance pool
  • Reserved instance pools in Compute Cloud

Was the article helpful?

Previous
Configuring access permissions for a dedicated host group
Next
Updating a reserved instance pool
© 2026 Direct Cursus Technology L.L.C.