Quotas and limits

Yandex.Cloud services can be subject to quotas and limits:

  • Quotas are organizational restrictions that can be changed by technical support on request.
  • Limits are technical restrictions due to the Yandex.Cloud architecture specifics. The limits cannot be changed.

You can view your current account quotas in the management console.

When designing your infrastructure in Yandex.Cloud, consider the limits as the boundary of opportunities that Yandex Cloud can provide to you. Quotas are changeable restrictions that can potentially be increased to the values of limits.

Why quotas are needed

Quotas serve as a soft restriction for requesting resources, and allow Yandex Cloud to guarantee the stability of the service: new users cannot take up too much resources for testing purposes. If you are ready to use more resources, contact the technical support and tell us exactly which quotas you need to increase, and how.

Technical support decides whether or not to increase quotas on an individual basis.

Quotas and limits defaults for Yandex.Cloud services

Quotas are listed with default values that match the quotas of the trial period.

Yandex Compute Cloud

Quotas

Type of limit Value
Number of virtual machines per cloud 8
Total number of vCPUs for all VMs per cloud 8
Total virtual memory for all VMs per cloud 64 GB
Total number of disks per cloud 32
Total SSD storage capacity per cloud 50 GB
Total HDD storage capacity per cloud 200 GB
Total number of disk snapshots per cloud 32
Total storage capacity of all disk snapshots per cloud 400 GB
Number of images per cloud 8
Number of instance groups per cloud 10
Total number of GPUs for all VMs per cloud* 0
Number of concurrent operations in the cloud 15
Maximum number of VM instances in a placement group 5
Maximum number of placement groups per cloud 2

* To create a VM with a GPU, contact technical support.

VM limits

Type of limit Value
Maximum number of vCPUs per VM 32 and 64 for Intel Broadwell and Intel Cascade Lake platforms, respectively
Maximum virtual memory per VM 256 GB and 512 GB for Intel Broadwell and Intel Cascade Lake platforms, respectively
Maximum number of disks connected to a single VM 7
Maximum number of GPUs connected to a single VM 4
Maximum number of vCPUs for VMs with GPUs 32
Maximum RAM for VMs with GPUs 384

Disk limits

Type of limit Value
Maximum disk size 4 TB
Maximum disk snapshot size 4 TB
Allocation unit size 32 GB
Maximum* IOPS for writes, per disk 40,000
Maximum* IOPS for writes, per allocation unit 1000
Maximum** bandwidth for writes, per disk 450 MB/s
Maximum** bandwidth for writes, per allocation unit 15 MB/s
Maximum* IOPS for reads, per disk 12,000
Maximum* IOPS for reads, per allocation unit 400
Maximum** bandwidth for reads, per disk 450 MB/s
Maximum** bandwidth for reads, per allocation unit 15 MB/s
Type of limit Value
Maximum disk size 4 TB
Maximum disk snapshot size 4 TB
Allocation unit size 256 GB
Maximum* IOPS for writes, per disk 11,000
Maximum* IOPS for writes, per allocation unit 300
Maximum** bandwidth for writes, per disk 240 MB/s
Maximum** bandwidth for writes, per allocation unit 30 MB/s
Maximum* IOPS for reads, per disk 300
Maximum* IOPS for reads, per allocation unit 100
Maximum** bandwidth for reads, per disk 240 MB/s
Maximum** bandwidth for reads, per allocation unit 30 MB/s
*

To achieve maximum IOPS, we recommend performing read and write operations that are 4 KB and less.

**

To achieve the maximum possible bandwidth, we recommend performing 4 MB reads and writes.

Yandex Object Storage

Quotas

Type of limit Value
Storage volume in a cloud 5 TB
Number of buckets per cloud 25

Limits

Type of limit Value
Maximum object size 5 TB
Total header size per request to the HTTP API 8 KB
Size of user-defined metadata in an object 2 KB
Maximum size of data to be uploaded per request 5 GB
Minimum size of data parts for multipart uploading, except the last one 5 MB
Maximum number of parts in multi-part uploading 10,000

Yandex Virtual Private Cloud

Quotas

Type of limit Value
Number of cloud networks per cloud 2
Number of subnets per cloud 6
Number of static public IP addresses per cloud 2
Number of route tables per cloud 8
Number of static routes per cloud 256

Limits

Type of limit Value
Minimum CIDR size for a subnet /28
Maximum CIDR size for a subnet /16
Maximum number of simultaneous TCP/UDP connections per VM 50000

Filtering outgoing traffic

Yandex.Cloud always blocks outgoing traffic to TCP port 25:

  • To any servers on the internet other than Yandex.Mail servers.
  • To Yandex Compute Cloud VMs when accessed via a public IP address.

Yandex.Cloud may open TCP port 25 by request via technical support if you comply with Acceptable Use Policy. Yandex.Cloud is entitled to block outgoing traffic on TCP port 25 if you violate the Use Policy.

Yandex Resource Manager

There are no quotas or limits for Yandex Resource Manager.

Yandex Load Balancer

Quotas

Type of limit Value
Number of load balancers per cloud 2
Number of target groups per cloud 2

Limits

Type of limit Value
Number of resources per target group 254
Number of listening ports 10
Number of health checks per attached target group 1
Status check protocol TCP, HTTP

Other restrictions

A particular target group can only contain target resources from a single cloud network.

A target group can include resources that are connected to the same subnet within a single availability zone.

You can create a load balancer without a listener.

Health checks are transmitted from the IP address range 198.18.235.0/24.

When connecting resources to the load balancer, keep in mind the limit on the maximum number of simultaneous TCP/UDP connections per VM.

Yandex Managed Service for ClickHouse

Quotas

Type of limit Value
Number of clusters per cloud 8
Total number of processor cores for all DB hosts per cloud 8
Total virtual memory for all DB hosts per cloud 32 GB
Total storage capacity for all clusters per cloud 200 GB

Limits

Type of limit Value
Lowest host class s1.nano (1 vCPU, 4 GB RAM)
Highest host class s1.xlarge (32 vCPUs, 128 GB RAM)
Maximum number of hosts in the cluster 10
Maximum network storage capacity 4096 GB
Maximum local storage capacity 1400 GB

Yandex Managed Service for MongoDB

Quotas

Type of limit Value
Number of clusters per cloud 8
Total number of processor cores for all DB hosts per cloud 8
Total virtual memory for all DB hosts per cloud 32 GB
Total storage capacity for all clusters per cloud 200 GB

Limits

Type of limit Value
Lowest host class s1.nano (1 vCPU, 4 GB RAM)
Highest host class s1.xlarge (32 vCPUs, 128 GB RAM)
Maximum number of hosts per cluster MongoDB 5
Maximum storage capacity for a cluster MongoDB 512 GB

Yandex Managed Service for MySQL

Quotas

Type of limit Value
Number of clusters per cloud 8
Total number of processor cores for all DB hosts per cloud 8
Total virtual memory for all DB hosts per cloud 32 GB
Total storage capacity for all clusters per cloud 200 GB

Limits

Type of limit Value
Lowest host class b1.nano (5% × 2 vCPU Intel Broadwell, 2 GB RAM)
Highest host class s2.5xlarge (48 vCPU Intel Cascade Lake, 192 GB RAM)
Maximum number of hosts per cluster 7
Maximum network storage capacity 2048 GB
Maximum local storage capacity 1400 GB

Yandex Managed Service for PostgreSQL

Quotas

Type of limit Value
Number of clusters per cloud 8
Total number of processor cores for all DB hosts per cloud 8
Total virtual memory for all DB hosts per cloud 32 GB
Total storage capacity for all clusters per cloud 200 GB

Limits

Type of limit Value
Lowest host class s1.nano (1 vCPU, 4 GB RAM)
Highest host class s1.xlarge (32 vCPUs, 128 GB RAM)
Maximum number of hosts per cluster 10
Maximum network storage capacity 2048 GB
Maximum local storage capacity 1400 GB

Yandex Managed Service for Redis

Quotas

Type of limit Value
Number of clusters per cloud 8
Total number of processor cores for all DB hosts per cloud 8
Total virtual memory for all hosts per cloud 32 GB
Total disk storage capacity for all clusters per cloud 200 GB

Limits

Type of limit Value
Lowest host class b1.nano (burstable with 2 GB RAM)
Highest host class hm1.9xlarge (high-memory with 256 GB RAM)
Maximum number of hosts per cluster 7
Minimum disk size per cluster 2 times more than the amount of RAM selected
Maximum disk size per cluster 8 times more than the amount of RAM selected

Yandex Message Queue

Quotas

Messages
Type of limit Value
Number of SendMessage and SendMessageBatch calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of ReceiveMessage calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of DeleteMessage and DeleteMessageBatch calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of CreateQueue calls per cloud 2 calls per second
Number of DeleteQueue calls per cloud 5 calls per second
Number of other request calls per cloud 100 calls per second
Number of queues per cloud 10

Limits

Queues
Type of limit Value
Minimum message enqueue delay (DelaySeconds parameter) 0 seconds
Maximum message enqueue delay (DelaySeconds parameter) 900 seconds (15 minutes)
Number of messages being processed per standard queue 120,000
Number of messages being processed per FIFO queue 20,000
Queue name Maximum of 80 characters, including numbers, small and capital Latin letters, hyphens, and underscores. The name of a FIFO queue must end with the .fifo suffix.
Messages
Type of limit Value
Batch entry ID Maximum of 80 characters, including numbers, small and capital Latin letters, hyphens, and underscores.
Maximum number of message attributes 10
Maximum number of entries per batch 10
Message content XML, JSON, and unformatted text. The following Unicode characters are supported:
  • #x9
  • #xA
  • #xD
  • from #x20 to #xD7FF
  • from #xE000 to #xFFFD
  • from #x10000 to #x10FFFF
Maximum period for retaining messages in a queue 1209600 seconds (14 days)
Minimum period for retaining messages in a queue 60 seconds (1 minute)
Maximum message enqueue delay (DelaySeconds parameter) 900 seconds (15 minutes)
Minimum message enqueue delay (DelaySeconds parameter) 0 seconds
Maximum message size 262144 bytes (256 KB)
Minimum message size 1 byte
Maximum message visibility timeout 12 hours
Minimum message visibility timeout 0 seconds
Maximum clients waiting time to wait for the message from an empty queue (WaitTimeSeconds parameter) 20 seconds

Yandex SpeechKit

Quotas

Type of limit Value
Short audio recognition
Requests per second 20
Streaming mode of short audio recognition
Requests per second 40
Long audio recognition
Recognition requests per hour 500
Operation status check requests per hour 2500
Billable hours of audio per day 10,000
Speech synthesis
Requests per second 40

Limits

Type of limit Value
Short audio recognition
Maximum file size 1 MB
Maximum duration of audio 30 seconds
Maximum number of audio channels 1
Streaming mode of short audio recognition
Maximum duration of transmitted audio for the entire session 5 minutes
Maximum size of transmitted audio data 10 MB
Maximum number of audio channels 1
Long audio recognition
Maximum file size 1 GB
Maximum duration of audio 4 hours
Period for storing recognition results on the server 3 days

Yandex Translate

Quotas

Type of limit Value
Calls of a single API method per second 20
Characters sent for translation per hour 1 million
Characters sent for language detection per hour 1 million

Limits

There are no limits in the service. For limitations on the field values in the request body, see the API reference.

Yandex Vision

Quotas

Type of limit Value
Number of requests per second 10
Text recognition attempts per second 5
Face detection attempts per second 5
Image classification attempts per second 5

Limits

Type of limit Value
Maximum file size 1 MB
Maximum image size 20 MP (length × width)
Maximum number of pages in a PDF file 8