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
    • Yandex SIEM
    • 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
    • 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:

  • Quotas
  • Quotas for instances and instance groups
  • vCPU quotas
  • GPU quotas
  • Disk quotas
  • File storage quotas
  • Image quotas
  • Snapshot quotas
  • Dedicated host quotas
  • Other quotas
  • Limits
  • VM limits
  • VM limits related to disks
  • Disk and file storage limits
  • Limits of disk snapshot schedules
  • Other limits
  1. Concepts
  2. Quotas and limits

Quotas and limits in Compute Cloud

Written by
Yandex Cloud
Improved by
amatol
Updated at September 4, 2026
View in Markdown
  • Quotas
    • Quotas for instances and instance groups
    • vCPU quotas
    • GPU quotas
    • Disk quotas
    • File storage quotas
    • Image quotas
    • Snapshot quotas
    • Dedicated host quotas
    • Other quotas
  • Limits
    • VM limits
    • VM limits related to disks
    • Disk and file storage limits
    • Limits of disk snapshot schedules
    • Other limits

The reserved instance pool feature is at the Preview stage.

Compute Cloud has the following limitations:

  • Quotas are organizational constraints that can be changed by contacting technical support.
  • Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

If you need more resources, you can increase your quotas in one of the following ways:

  • Make a request to increase your quotas.
  • Contact support and specify which quotas you want increased and by how much.

To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g., editor or admin.

You can manage your quotas with Cloud Quota Manager.

QuotasQuotas

Quotas for instances and instance groupsQuotas for instances and instance groups

Type of limit

Value

Number of virtual machines per cloud
compute.instances.count

12

Total VM RAM per cloud1
compute.instanceMemory.size

128 GB

Number of instance groups per cloud
compute.instanceGroups.count

10

Number of placement groups per cloud
compute.placementGroups.count

2

Maximum number of VMs per partition in a VM placement group with the partition placement strategy

100

Maximum number of security groups per network interface

Warning

You can increase this quota only upon agreement with your account manager.

5

vCPU quotasvCPU quotas

Type of limit

Value

Number of vCPUs for instances per cloud1
compute.instanceCores.count

32

Number of vCPUs for Compute Optimized instances per cloud1
compute.instanceHighFreqCores.count

0

GPU quotasGPU quotas

Type of limit

Value

Number of NVIDIA® Tesla® V100 GPUs per cloud1
compute.instanceGpus.count

0

Number of NVIDIA® Ampere® A100 GPUs per cloud1
compute.instanceA100Gpus.count

0

Number of GPUs powered by AMD EPYC™ 9474F with Gen2 per cloud1
compute.instanceV3IGpus.count

0

Number of NVIDIA® Tesla® T4 GPUs per cloud1
compute.instanceT4Gpus.count

0

Number of NVIDIA® Tesla® T4 GPUs per cloud in the ru-central1-d availability zone1
compute.instanceT4Gpus.count.ru-central1-d

0

Number of GPUs powered by Intel Ice Lake with T4i per cloud1
compute.instanceT4IGpus.count

0

Disk quotasDisk quotas

Type of limit

Value

Number of disks per cloud
compute.disks.count

32

Total HDD capacity per cloud
compute.hddDisks.size

500 GB

Total SSD capacity per cloud
compute.ssdDisks.size

200 GB

Total size of non-replicated SSDs per cloud
compute.ssdNonReplicatedDisks.size

558 GB

Total size of high-performance SSDs per cloud
compute.ssdIOM3Disks.size

186 GB

Number of disk placement groups per cloud
compute.diskPlacementGroups.count

5

File storage quotasFile storage quotas

Type of limit

Value

Number of network file storages per cloud
compute.filesystems.count

100

Total network file storage HDD capacity per cloud
compute.hddFilesystems.size

512 GB

Total network file storage SSD capacity per cloud
compute.ssdFilesystems.size

512 GB

Image quotasImage quotas

Type of limit

Value

Number of images per cloud
compute.images.count

32

Total size of images per cloud
compute.images.size

1,024 GB

Number of images optimized for deployment per cloud2
compute.diskPools.count

0

Note

When deploying optimized images, the quotas for the number of images per cloud and the total volume of images per cloud also apply. If you need to, send a request to support to increase these quotas.

Snapshot quotasSnapshot quotas

Type of limit

Value

Number of disk snapshots per cloud
compute.snapshots.count

32

Total volume of disk snapshots per cloud
compute.snapshots.size

400 GB

Number of schedules for disk snapshots per cloud
compute.snapshotSchedules.count

32

Dedicated host quotasDedicated host quotas

Type of limit

Value

Number of dedicated hosts per cloud2
compute.dedicatedHosts.count

0

Number of dedicated host groups per cloud
compute.hostGroups.count

6

Other quotasOther quotas

Type of limit

Value

Number of concurrent operations per folder

15

Number of reserved instance pools per cloud2
compute.reservedInstancePools.count

1

1 This quota includes resources associated with vacant slots in reserved instance pools.

2 To increase quotas for deployment-optimized images, dedicated hosts, or reserved instance pools, contact support.

LimitsLimits

VM limitsVM limits

Limits per VM depend on the VM platform:

Intel Broadwell
Intel Cascade Lake
Intel Ice Lake
Intel Ice Lake (Compute Optimized)

Type of limit

Value

Maximum number of vCPUs per VM

32

Maximum virtual memory per VM

Without GPU

256 GB

With GPU

384 GB

Maximum number of GPUs connected to a single VM

4

Maximum number of disks and file storages connected to a single VM3

PCI_TOPOLOGY_V1 bus topology.

Number of VCPUs <= 18

8

Number of VCPUs > 18

164

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

62

Number of VCPUs >= 6

80

Maximum number of network interfaces connected to a single VM

Bus topology
PCI_TOPOLOGY_V1

84

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

20

Number of VCPUs >= 6

32

Maximum number of VMs per VM placement group with the spread placement strategy

5

Type of limit

Value

Maximum number of vCPUs per VM

Without GPU

80

With GPU

64

Maximum virtual memory per VM

Without GPU

1,280 GB

With GPU

384 GB

Maximum number of GPUs connected to a single VM

8

Maximum number of disks and file storages connected to a single VM3

PCI_TOPOLOGY_V1 bus topology.

Number of VCPUs <= 20

8

Number of VCPUs > 20

164

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

62

Number of VCPUs >= 6

80

Maximum number of network interfaces connected to a single VM

Bus topology
PCI_TOPOLOGY_V1

84

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

20

Number of VCPUs >= 6

32

Maximum number of VMs per VM placement group with the spread placement strategy

5

Type of limit

Value

Maximum number of vCPUs per VM

96

Maximum virtual memory per VM

640 GB

Maximum number of disks and file storages connected to a single VM3

PCI_TOPOLOGY_V1 bus topology.

Number of VCPUs <= 32

8

Number of VCPUs > 32

164

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

62

Number of VCPUs >= 6

80

Maximum number of network interfaces connected to a single VM

Bus topology
PCI_TOPOLOGY_V1

84

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

20

Number of VCPUs >= 6

32

Maximum number of VMs per VM placement group with the spread placement strategy

5

Type of limit

Value

Maximum number of vCPUs per VM

56

Maximum virtual memory per VM

448 GB

Maximum number of disks and file storages connected to a single VM3

PCI_TOPOLOGY_V1 bus topology.

Number of VCPUs <= 32

8

Number of VCPUs > 32

164

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

62

Number of VCPUs >= 6

80

Maximum number of network interfaces connected to a single VM

Bus topology
PCI_TOPOLOGY_V1

84

PCI_TOPOLOGY_V2 bus topology

Number of VCPUs <= 4

20

Number of VCPUs >= 6

32

Maximum number of VMs per VM placement group with the spread placement strategy

5

3 Including the boot disk.

4 At startup, you can connect no more than 14 devices to a VM, including the boot disk and network card. You should connect other devices when your VM is already running. Please note that if you restart a VM with more than 14 devices connected, it will not be able to boot.

Warning

To guarantee the operability and performance of VMs with large numbers of disk devices and network interfaces, such numbers of devices and interfaces must be supported not by the VM hardware generation alone but by the OS as well, plus provided with enough vCPUs and RAM.

VM limits related to disksVM limits related to disks

The values listed below are VM side limitations. They scale with the number of vCPUs: the row value is multiplied by the number of vCPUs to set the upper boundary of the total load on all disks attached to the VM. For example, for a VM with 4 vCPUs and a network SSD, the total maximum IOPS cannot exceed 4 × 3,500 = 14,000.

The actual performance of an individual disk is also capped by its own limits. The final value is determined as the minimum of the two: the VM limit and the disk limit.

Note

IOPS and bandwidth limits of an individual disk depend on the number of allocation units. For more information, see Disk and file storage performance.

Network SSD
Network HDD
Non-replicated SSD
Ultra high-speed network storage with three replicas (SSD)
Type of limit Value
Maximum5 IOPS per VM vCPU 3,500
Maximum6 bandwidth per VM vCPU 45 MB/s
Type of limit Value
Maximum5 IOPS per VM vCPU 3,500
Maximum6 bandwidth per VM vCPU 45 MB/s
Type of limit Value
Total number of non-replicated SSDs per placement group 8
Maximum5 IOPS per VM vCPU 10,000
Maximum5 IOPS per VM 100,000
Maximum6 bandwidth per VM vCPU 100 MB/s
Maximum6 bandwidth per VM 1 GB/s
Type of limit Value
Maximum5 IOPS per VM vCPU 10,000
Maximum5 IOPS per VM 100,000
Maximum6 bandwidth per VM vCPU 100 MB/s
Maximum6 bandwidth per VM 1 GB/s

Disk and file storage limitsDisk and file storage limits

Network SSD
Network HDD
Non-replicated SSD
Ultra high-speed network storage with three replicas (SSD)
Type of limit Value
Maximum disk size 256 TB
Allocation unit size 32 GB
Maximum5 IOPS for writes per disk 40,000
Maximum5 IOPS for writes per allocation unit 1,000
Maximum6 bandwidth for writes per disk 450 MB/s
Maximum6 bandwidth for writes per allocation unit 15 MB/s
Maximum5 IOPS for reads per disk 20,000
Maximum5 IOPS for reads per allocation unit 1,000
Maximum6 bandwidth for reads per disk 450 MB/s
Maximum6 bandwidth for reads per allocation unit 15 MB/s
Type of limit Value
Maximum disk size 256 TB
Allocation unit size 256 GB
Maximum5 IOPS for writes per disk 11,000
Maximum5 IOPS for writes per allocation unit 300
Maximum6 bandwidth for writes per disk 240 MB/s
Maximum6 bandwidth for writes per allocation unit 30 MB/s
Maximum5 IOPS for reads per disk 2,000
Maximum5 IOPS for reads per allocation unit 300
Maximum6 bandwidth for reads per disk 240 MB/s
Maximum6 bandwidth for reads per allocation unit 30 MB/s
Type of limit Value
Minimum non-replicated disk size 93 GB
Allocation unit size 93 GB
Maximum5 IOPS for writes per disk 75,000
Maximum5 IOPS for writes per allocation unit 5,600
Maximum6 bandwidth for writes per disk 1 GB/s
Maximum6 bandwidth for writes per allocation unit 82 MB/s
Maximum5 IOPS for reads per disk 75,000
Maximum5 IOPS for reads per allocation unit 28,000
Maximum6 bandwidth for reads per disk 1 GB/s
Maximum6 bandwidth for reads per allocation unit 110 MB/s
Type of limit Value
Minimum capacity of ultra high-speed network storage with three replicas (SSD) 93 GB
Allocation unit size 93 GB
Maximum5 IOPS for writes per disk 40,000
Maximum5 IOPS for writes per allocation unit 5,600
Maximum6 bandwidth for writes per disk 1 GB/s
Maximum6 bandwidth for writes per allocation unit 82 MB/s
Maximum5 IOPS for reads per disk 75,000
Maximum5 IOPS for reads per allocation unit 28,000
Maximum6 bandwidth for reads per disk 1 GB/s
Maximum6 bandwidth for reads per allocation unit 110 MB/s
SSD storage
HDD storage
Type of limit Value
Maximum storage size 8 TB
Allocation unit size 32 GB
Maximum number of files in storage 1,000,000
Maximum size of file in storage 300 GB
Type of limit Value
Maximum storage size 8 TB
Allocation unit size 256 GB
Maximum number of files in storage 1,000,000
Maximum size of file in storage 300 GB

Read and write operations utilize the same disk resource. The more read operations you do, the fewer write operations you can do, and vice versa. For more information, see Read and write operations.

5 For maximum IOPS, we recommend keeping your read and write operations close to the disk block size (4 KB by default).

6 For maximum bandwidth, we recommend 4 MB reads and writes.

Limits of disk snapshot schedulesLimits of disk snapshot schedules

Type of limit Value
Number of disks added to a schedule 1,000
Number of schedules a disk is added to 1,000

Other limitsOther limits

Type of limit Value
Time to complete processes when stopping a VM7 30 seconds

7 When a VM stops, the hypervisor sends a shutdown signal to the VM operating system. The OS has 30 seconds to gracefully terminate all running processes to avoid data loss. After this time elapses, the VM will be forcibly terminated.

Was the article helpful?

Previous
Backups
Next
Access management
© 2026 Direct Cursus Technology L.L.C.