Yandex Cloud service quotas and limits
- Why quotas are needed
- Default quotas and limits for Yandex Cloud services
- Yandex API Gateway
- Yandex Application Load Balancer
- Yandex Audit Trails
- Yandex Certificate Manager
- Yandex Cloud Backup
- Yandex BareMetal
- Yandex Cloud Billing
- Yandex Cloud CDN
- Yandex Cloud Desktop
- Yandex Cloud DNS
- Yandex Foundation Models
- Yandex Cloud Functions
- Yandex Cloud Interconnect
- Yandex Cloud Logging
- Yandex Cloud Notification Service
- Yandex Cloud Organization
- Yandex Cloud Postbox
- Yandex Cloud Video
- Yandex Compute Cloud
- Quotas
- Limits
- VM limits
- VM limits on disk operations
- Disk and file storage limits
- Limits of disk snapshot schedules
- Other limits
- Yandex Container Registry
- Yandex Data Processing
- Yandex Data Streams
- Yandex Data Transfer
- Yandex DataLens
- Yandex DataSphere
- Yandex Identity and Access Management
- Yandex IoT Core
- Yandex Key Management Service
- Yandex Load Testing
- Yandex Lockbox
- Yandex Managed Service for Apache Airflow™
- Yandex Managed Service for Apache Kafka®
- Yandex Managed Service for ClickHouse®
- Yandex Managed Service for GitLab
- Yandex Managed Service for Greenplum®
- Yandex Managed Service for Kubernetes
- Yandex Managed Service for MongoDB
- Yandex Managed Service for MySQL®
- Yandex Managed Service for OpenSearch
- Yandex Managed Service for PostgreSQL
- Yandex Managed Service for Valkey™
- Yandex Managed Service for YDB
- Yandex Message Queue
- Yandex MetaData Hub
- Yandex Monitoring
- Yandex Network Load Balancer
- Yandex Object Storage
- Yandex Query
- Yandex Resource Manager
- Yandex Search API
- Yandex Serverless Containers
- Yandex SmartCaptcha
- Yandex Smart Web Security
- Yandex SpeechKit
- Yandex SpeechSense
- Yandex Translate
- Yandex Virtual Private Cloud
- Yandex Vision OCR
- Yandex WebSQL
Yandex Cloud services can be subject to quotas and limits:
- Quotas are organizational constraints that our support team can change upon request.
- Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.
When designing your infrastructure in Yandex Cloud, plan for the maximum limits that Yandex Cloud can provide you with. Quotas are modifiable constraints that can potentially be increased up to the limit values. Quotas do not guarantee that resources are available.
Why quotas are needed
Quotas serve as a soft constraint for requesting resources and allow you to manage cloud service usage: with quotas, new users cannot take up too much resources for testing purposes.
If ready to use more resources, you can increase your quotas in the following ways:
- Generate a request for a quota increase.
- Contact support and tell us which quotas you want increased and by how much.
To have your request processed, you must have the quota-manager.requestOperator role or higher (editor or admin).
You can manage quotas with Cloud Quota Manager.
Default quotas and limits for Yandex Cloud services
Quotas are listed with default values that match the quotas of the trial period.
Yandex API Gateway
Quotas
| Limit type | Value |
|---|---|
| Number of triggers per cloud | 100 |
Limits
| Limit type | Value |
|---|---|
| Maximum size of a request to and a response from API Gateway | 2.5 MB |
| Maximum specification size | 3.5 MB |
| Maximum request processing timeout | 10 minutes1 |
| Maximum size of message being transmitted via a web socket | 128 KB |
| Maximum size of frame being transmitted via a web socket | 32 KB |
| Maximum time-to-live of a web socket connection | 60 minutes |
| Maximum time-to-live of an idle web socket connection | 10 minutes |
| Maximum number of triggers per message queue | 1 |
| Maximum message size per trigger2 | 230 KB |
| Maximum number of domains you can connect to a single API gateway | 20 |
| Number of user networks per cloud | 1 |
1 Default value: 5 minutes.
2 The message may include service metadata, which will reduce the maximum message size.
Yandex Application Load Balancer
Quotas
| Limit type | Value |
|---|---|
| Maximum number of load balancers per cloud | 4 |
| Maximum number of HTTP routers per cloud | 16 |
| Maximum number of backend groups per cloud | 32 |
| Maximum number of target groups per cloud | 32 |
Limits
| Limit type | Value |
|---|---|
| Maximum number of resources per target group | 256 |
| Maximum number of backends per backend group | 8 |
| Maximum number of virtual hosts per HTTP router | 64 |
| Maximum number of routes per HTTP router | 128 |
| Maximum number of listeners per L7 load balancer | 8 |
| Maximum number of SNI listeners per L7 load balancer | 32 |
| Maximum number of authority headers you can specify for a virtual host | 32 |
Yandex Audit Trails
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of trails per cloud | 3 |
Yandex Certificate Manager
Quotas
| Type of limit | Value |
|---|---|
| Number of certificates per cloud | 20 |
| Number of domains per cloud | 10 |
Limits for Let's Encrypt® certificates
| Type of limit | Value |
|---|---|
| Number of domains per certificate | 100 |
| Number of certificates per domain | 50 per week |
| Number of certificates per domain set | 5 per week |
See also
Yandex Cloud Backup
Quotas
| Type of limit | Value |
|---|---|
| Number of virtual machines connected to Cloud Backup per cloud1 | 50 |
| Total size of backups per cloud | 10 TB |
1 To consider a virtual machine connected to Cloud Backup, it has to be linked to at least one backup policy. If the quota is exceeded, you will not be able to link new VMs to backup policies.
Yandex BareMetal
Quotas
| Type of limit | Value |
|---|---|
| Number of servers | 2 |
| Number of VRFs | 20 |
| Number of subnets | 10 |
| Number of images | 10 |
Yandex Cloud Billing
Quotas
| Limit type | Value |
|---|---|
| Number of budgets per billing account | 20 |
| Number of clouds linked to a single billing account | 5 |
| Number of Tracker instances linked to a single billing account | 5 |
| Number of DataSphere communities linked to a single billing account | 100 |
Limits
To find out the current service limits, contact support.
Yandex Cloud CDN
Quotas
| Type of limit | Value |
|---|---|
| Number of CDN resources per cloud | 20 |
Limits
| Type of limit | Value |
|---|---|
| Number of requests for cache purging per minute | 1 |
| Number of file paths per cache purging request | 10 |
| Number of requests for preloading files per minute | 1 |
| Number of paths to preloaded files per request | 100 |
| Number of IP addresses (subnet prefixes) in the IP address access policy list | 100 |
Yandex Cloud Desktop
Quotas
| Limit type | Value |
|---|---|
| Maximum number of desktops per cloud | 5 |
| Maximum total number of vCPUs per cloud | 10 |
| Maximum total amount of RAM per cloud | 20 GB |
| Maximum total HDD space per cloud | 500 GB |
| Maximum total SSD space per cloud | 500 GB |
Yandex Cloud DNS
Quotas
| Type of limit | Value |
|---|---|
| Number of zones per cloud | 100 |
| Number of record sets per cloud | 1,000 |
| Number of record sets per zone | 100 |
Limits
| Type of limit | Value |
|---|---|
| Maximum number of records per record set | 100 |
| Maximum number of simultaneously updated record sets | 1,000 |
| Maximum number of networks per zone | 50 |
Yandex Foundation Models
Quotas
| Type of limitation | Value |
|---|---|
| Text vectorization | |
| Number of text vectorization requests per second | 10 |
| Text generation | |
| Number of concurrent generations in synchronous mode, YandexGPT Lite model | 10 |
| Number of concurrent generations in synchronous mode, YandexGPT Pro model | 10 |
| Number of concurrent generations, YandexGPT Pro 32k | 1 |
| Number of concurrent generations in synchronous mode, Llama 8b1 model | 10 |
| Number of concurrent generations, Llama 70b model | 1 |
| Number of requests per second, asynchronous mode (request) | 10 |
| Number of requests per second, asynchronous mode (getting a response) | 50 |
| Number of requests per hour, asynchronous mode (request) | 5,000 |
| Number of tokenization requests per second | 50 |
| Model working mode: Batch | |
| Number of runs per hour | 10 |
| Number of runs per day | 100 |
| Text classification | |
| Number of text classification requests per second | 1 |
| Image generation | |
| Number of generation requests per minute | 500 |
| Number of generation requests per day | 5,000 |
| Number of result requests per second | 50 |
| Model tuning | |
| Number of fine-tuning runs per day | 10 |
| Number of fine-tuning runs per hour | 3 |
| Datasets | |
| Number of uploaded datasets | 100 |
| Maximum size of one dataset | 5 GB |
| Total size of datasets | 300 GB |
Limits
| Type of limitation | Value |
|---|---|
| Period to store results of asynchronous requests on the server | 3 days |
| Text vectorization | |
| Number of input tokens | 2,000 |
| Output vector size | 256 |
| Text generation | |
| Maximum number of tokens in response via API | 2,000 |
| Maximum number of tokens per response in the management console | 1,000 |
| Total number of tokens in request and response, 3rd generation models | 8192 |
| Total number of tokens in request and response, 4th generation YandexGPT Lite model | 8192 |
| Total number of tokens in request and response, 5th generation YandexGPT Lite model | 32,000 |
| Total number of tokens in request and response, synchronous mode of the 4th generation YandexGPT Pro model | 8192 |
| Total number of tokens in request and response, asynchronous mode of the 4th generation YandexGPT Pro model | 32,000 |
| Total number of tokens in request and response, YandexGPT Pro 32k model | 32,000 |
| Total number of tokens in request and response, 5th generation YandexGPT Pro model | 32,000 |
| Number of free requests per hour for users without a billing account. Available only in the management console | 10 |
| Assistants | |
| Maximum number of assistants | 1,000 |
| Maximum number of threads | 10,000 |
| Maximum number of users | 10,000 |
| Maximum number of files to upload | 10,000 |
| Maximum file size | 128 MB |
| Number of files per upload | 100 |
| Maximum number of files per search index | 10,000 |
| Maximum number of messages per thread | 100,000 |
| Maximum number of search indexes | 1,000 |
| Maximum number of indexing operations to run | 10 |
| Image generation | |
| Maximum prompt length | 500 characters |
| Number of free requests per minute for users without a billing account. Available only in the management console | 2 |
| Number of free requests per day for users without a billing account. Available only in the management console | 10 |
1 Llama was created by Meta. Meta is designated as an extremist organization and its activities are prohibited in Russia.
Yandex Cloud Functions
Quotas
| Type of limit | Value |
|---|---|
| Number of triggers per cloud | 100 |
| Number of functions per cloud | 10 |
| Number of tags per function | 10 |
| Number of concurrent function calls (for all functions in each availability zone) | 10 |
| Number of function instances per availability zone | 10 |
| Total RAM for all running functions per availability zone | 20 GB |
| Number of provisioned function instances per cloud | 2 |
| Number of concurrent operations on a single function and its versions | 10 |
| Number of concurrent operations on all functions and their versions per folder | 15 |
| Number of concurrent operations on all functions and their versions per cloud | 20 |
| Number of network packets per second per function instance | 10,000 |
For more information about relationships between quotas, see Relationship between quotas.
Limits
| Type of limit | Value |
|---|---|
| Maximum uploaded file size | |
| ZIP archive from the management console | 3.5 MB |
| ZIP archive from S3 bucket | 128 MB |
| Unzipped ZIP archive from S3 bucket | 680 MB |
| Other restrictions | |
| Maximum size of the JSON structure of a request and response | 3.5 MB |
| Maximum size of temporary files | 512 MB |
| Maximum function execution time before timeout, including first call initialization1 | 1 hour |
| Maximum RAM per function instance | 8 GB |
| Maximum total environment variable storage, including variable names2 | 4 KB |
| Maximum number of triggers per message queue | 1 |
| Maximum message size per trigger3 | 230 KB |
| Number of user networks per cloud | 1 |
1 A timeout longer than ten minutes is only available for long-lived functions.
2 Lockbox secrets are provided via environment variables and are also counted towards this limit.
3 The message may include service metadata, which will reduce the maximum message size.
Other restrictions
When installing dependencies:
- The total time for installing dependencies is limited to five minutes. After it expires, the build will fail with an error.
- For dependency installation, 1 GB of RAM is allocated, of which 700 MB is allocated for temporary file storage (tmpfs). Memory is consumed by active processes and files created and downloaded during the build.
- 50% of the CPU is available.
If the build takes longer than five minutes or requires more resources, build the dependencies yourself and download the function as a ZIP archive.
Yandex Cloud Interconnect
Quotas
| Type of limit | Value |
|---|---|
| Number of private connections per trunk | 2 |
| Number of public connections per trunk | 1 |
Limits
| Type of limit | Value |
|---|---|
| Maximum number of prefixes announced by the customer over BGP per private connection | 500 |
Yandex Cloud Logging
Quotas
| Type of limit | Value |
|---|---|
| Number of custom log groups per cloud | 10 |
| Maximum write speed | 1,000 entries per second |
| Maximum record retention period | 31 days |
There is no guarantee that records will be deleted as soon as the specified retention period expires: they may be deleted later.
Limits
| Type of limit | Value |
|---|---|
| Adding records | |
| Maximum number of records per request | 100 |
| Maximum record size | 1.6 MB |
Maximum message size |
0.8 MB |
Maximum json-payload size |
0.8 MB |
| Reading records | |
| Maximum number of requests per second | 5 |
| Other restrictions | |
| Minimum record retention period | 1 hour |
| Maximum filter length | 1,000 characters |
Yandex Cloud Notification Service
Limits
| Type of limit | Value |
|---|---|
| Maximum number of mobile push notification channels per cloud | 20 |
| Maximum number of in-browser push notification channels per cloud | 10 |
| Maximum number of SMS notification channels per cloud | 10 |
| Maximum number of SMS notification channels with a shared sender per cloud | 1 |
| Maximum number of SMS notification channels with an individual sender per cloud | 10 |
| Maximum number of test phone numbers per SMS notification channel | 10 |
| Maximum number of SMS messages per cloud1 | 100 per month |
| Maximum mobile push notification message size | 4 KB |
| Maximum browser push notification message size | 3 KB |
| Maximum SMS message length | 1,600 characters (10 segments) |
| Maximum name length for a push notification channel | 40 characters |
Maximum length for user data (CustomUserData) per mobile endpoint |
256 characters |
| Maximum length for a device ID per mobile endpoint | 256 characters |
| Maximum rate of requests to create or update notification channel attributes per cloud | 30 requests per second |
| Maximum rate of requests to send an SMS message per cloud | 20 requests per second |
| Maximum number of SMS messages to verify one test number | 5 per day for one number |
| Maximum number of SMS messages to verify test numbers per cloud | 20 per day |
1 Moving forward, the limit on the maximum number of SMS messages per cloud will become a quota. You will be able to increase it by contacting support.
Yandex Cloud Organization
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of subjects per organization | 10,000 |
| Maximum number of organizations a subject may belong to (quota for the subject) | 100 |
| Maximum number of invitations to an organization | 100 |
| Maximum number of organizations a subject may create | 10 |
| Maximum number of federations per organization | 10 |
| Maximum number of certificates per federation | 100 |
| Maximum number of subjects per federation | 10,000 |
| Maximum number of clouds per organization | 5 |
| Maximum number of access permission assignments per organization | 2,000 |
| Maximum number of OS Login profiles per organization | 4,000 |
| Maximum number of groups per organization | 100 |
| Maximum number of group members | 1,000 |
| Maximum number of groups a user may belong to | 1,000 |
Limits
There are no limits for Cloud Organization.
Yandex Cloud Postbox
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of email recipients | 10 |
| Maximum size of an email with attachments | 10 MB |
| Maximum number of addresses | 10 |
| Maximum email send rate | 1 email per second |
| Maximum number of emails that can be sent within a 24-hour time interval | 200 |
| Maximum number of configurations | 5 |
Yandex Cloud Video
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of simultaneous broadcasts per organization | 3 |
Limits
| Type of limit | Value |
|---|---|
| Maximum resolution of videos and broadcasts | 1080p |
| Maximum broadcast duration | 24 hours |
Yandex Compute Cloud
Quotas
Quotas for instances and instance groups
|
Type of limit |
Value |
|
Number of virtual machines per cloud |
12 |
|
Total virtual memory across all VMs per cloud |
128 GB |
|
Number of instance groups per cloud |
10 |
|
Maximum number of VM placement groups per cloud |
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 quotas
| Type of limit | Value |
|---|---|
| Total number of vCPUs across all VMs per cloud | 32 |
| Total number of Intel Ice Lake Compute-Optimized vCPUs across all VMs per cloud | 0 |
GPU quotas
| Type of limit | Value |
|---|---|
| Total number of NVIDIA® Tesla® V100 GPUs across all VMs per cloud | 0 |
| Total number of AMD EPYC™ with NVIDIA® Ampere® A100 GPUs across all VMs per cloud | 0 |
| Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs per cloud | 0 |
| Total number of Intel Ice Lake with T4i GPUs across all VMs per cloud | 0 |
Disk quotas
| Type of limit | Value |
|---|---|
| Total number of disks per cloud | 32 |
| Total HDD storage capacity per cloud | 500 GB |
| Total SSD storage capacity per cloud | 200 GB |
| Total non-replicated SSD storage capacity per cloud | 558 GB |
| Total capacity of ultra high-speed network SSD storages with three replicas per cloud | 186 GB |
| Number of non-replicated disk placement groups per cloud | 5 |
File storage quotas
| Type of limit | Value |
|---|---|
| Total number of file storages per cloud1 | 100 |
| Total HDD file storage size per cloud1 | 0 B |
| Total SSD file storage size per cloud1 | 0 B |
Image quotas
| Type of limit | Value |
|---|---|
| Number of images per cloud | 8 |
| Total volume of images per cloud | 1,024 GB |
| Number of images optimized for deployment per cloud1 | 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 quotas
| Type of limit | Value |
|---|---|
| Total number of disk snapshots per cloud | 32 |
| Total storage capacity of all disk snapshots per cloud | 400 GB |
| Number of disk snapshot schedules per cloud | 32 |
Dedicated host quotas
| Type of limit | Value |
|---|---|
| Number of dedicated hosts per dedicated host group1 | 0 |
| Number of dedicated host groups per cloud | 6 |
Other quotas
| Type of limit | Value |
|---|---|
| Number of concurrent operations per folder | 15 |
1 To increase quotas for file storages, deployment-optimized images, or dedicated hosts, contact support.
Limits
VM 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 disks and file storages connected to a single VM2 | Less than or equal to 18 vCPUs: 8 From 18 vCPUs: 163 |
| Maximum number of GPUs connected to a single VM | 4 |
| Maximum number of VM network interfaces | 83 |
| 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 disks and file storages connected to a single VM2 | Less than or equal to 20 vCPUs: 8 From 20 vCPUs: 163 |
| Maximum number of GPUs connected to a single VM | 8 |
| Maximum number of VM network interfaces | 83 |
| 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 VM2 | Less than or equal to 32 vCPUs: 8 More than> 32 vCPUs: 163 |
| Maximum number of VM network interfaces | 83 |
| 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 VM2 | Less than or equal to 32 vCPUs: 8 More than> 32 vCPUs: 163 |
| Maximum number of VM network interfaces | 83 |
| Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
2 Including the boot disk.
3 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.
VM limits on disk operations
Network SSD
Network HDD
Non-replicated SSD
Ultra high-speed network storage with three replicas (SSD)
Disk 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 |
| Maximum4 IOPS for writes per disk | 40,000 |
| Maximum4 IOPS for writes per allocation unit | 1,000 |
| Maximum5 bandwidth for writes per disk | 450 MB/s |
| Maximum5 bandwidth for writes per allocation unit | 15 MB/s |
| Maximum4 IOPS for reads per disk | 20,000 |
| Maximum4 IOPS for reads per allocation unit | 1,000 |
| Maximum5 bandwidth for reads per disk | 450 MB/s |
| Maximum5 bandwidth for reads per allocation unit | 15 MB/s |
| Type of limit | Value |
|---|---|
| Maximum disk size | 256 TB |
| Allocation unit size | 256 GB |
| Maximum4 IOPS for writes per disk | 11,000 |
| Maximum4 IOPS for writes per allocation unit | 300 |
| Maximum5 bandwidth for writes per disk | 240 MB/s |
| Maximum5 bandwidth for writes per allocation unit | 30 MB/s |
| Maximum4 IOPS for reads per disk | 2,000 |
| Maximum4 IOPS for reads per allocation unit | 300 |
| Maximum5 bandwidth for reads per disk | 240 MB/s |
| Maximum5 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 |
| Maximum4 IOPS for writes per disk | 75,000 |
| Maximum4 IOPS for writes per allocation unit | 5,600 |
| Maximum5 bandwidth for writes per disk | 1 GB/s |
| Maximum5 bandwidth for writes per allocation unit | 82 MB/s |
| Maximum4 IOPS for reads per disk | 75,000 |
| Maximum4 IOPS for reads per allocation unit | 28,000 |
| Maximum5 bandwidth for reads per disk | 1 GB/s |
| Maximum5 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 |
| Maximum4 IOPS for writes per disk | 40,000 |
| Maximum4 IOPS for writes per allocation unit | 5,600 |
| Maximum5 bandwidth for writes per disk | 1 GB/s |
| Maximum5 bandwidth for writes per allocation unit | 82 MB/s |
| Maximum4 IOPS for reads per disk | 75,000 |
| Maximum4 IOPS for reads per allocation unit | 28,000 |
| Maximum5 bandwidth for reads per disk | 1 GB/s |
| Maximum5 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.
4 For maximum IOPS, we recommend keeping your read and write operations close to the disk block size (4 KB by default).
5 For maximum bandwidth, we recommend 4 MB reads and writes.
Limits 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 limits
| Type of limit | Value |
|---|---|
| Time to complete processes when stopping a VM6 | 30 seconds |
6 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.
Yandex Container Registry
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of registries per cloud | 10 |
| Number of concurrent Docker image scans running in a single cloud | 10 |
Limits
| Type of limit | Value |
|---|---|
| Maximum size of a single layer of a Docker image | 150 GB |
| Maximum number of layers in a Docker image being scanned | 127 |
| Maximum number of Docker images in a single repository that can be checked by a trial run of the Docker image lifecycle policy | 50 000 |
| Maximum size of a Docker image to scan | 2 GB |
| Maximum number of Docker images to scan per request | 10 000 |
Yandex Data Processing
Quotas
Yandex Data Processing cluster VMs utilize your Yandex Compute Cloud cloud quotas.
Limits
| Type of limit | Value |
|---|---|
| Minimum host configuration | b2.medium (2 × 50% vCPU Intel Cascade Lake, 4 GB RAM) |
| Maximum host configuration | s3-c96-m576 (96 vCPU Intel Ice Lake, 576 GB RAM) |
| Maximum total number of subclusters | 12 |
| Maximum number of hosts per subcluster | 32 |
Maximum storage capacity per host on network HDDs (network-hdd) or SSDs (network-ssd) |
4,096 GB |
Maximum storage capacity per host on non-replicated network drives (network-ssd-nonreplicated) |
262074 GB |
Yandex Data Streams
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of data transmission streams | 10 |
| Maximum data retention period for a data stream | 24 hours |
Limits
| Type of limit | Value |
|---|---|
| Maximum data write requests per second for a single data stream segment | 1,000 RPS |
| Maximum data write speed for a single segment | 1 MB/s |
| Maximum single-segment data read speed for all standard consumers | 2 MB/s |
| Maximum number of dedicated data consumers per data stream | 5 consumers |
| Maximum size per message | 1 MB |
| Number of shards in a YDB serverless database | 100 |
Yandex Data Transfer
Quotas
| Type of limit | Value |
|---|---|
| Endpoints | 100 |
| Transfers | 50 |
| Running transfers | 10 |
Limits
| Type of limit | Value |
|---|---|
| Endpoints | 400 |
| Transfers | 200 |
| Running transfers | 50 |
Yandex DataLens
Quotas
There are no quotas for DataLens.
General limits
Note
DataLens has no limitation on the amount of data on the source you are connecting to.
| Type of limit | Value |
|---|---|
| Maximum number of DataLens instances per organization. | 1 |
| Maximum size of imported CSV file | 200 MB |
| Maximum number of tables in a single dataset | 32 |
| Maximum number of fields in a single dataset | 1200 |
| Maximum chart export size | 50 MB |
Chart data limits
Charts in DataLens can only display a limited amount of data. If the number of rows (columns and cells for pivot tables) in a dataset exceeds the established limit, the chart will not be built. Therefore, to build a chart from data in a large dataset, select a part of the data to display based on the limits below using the filters:
| Chart type | I/O |
|---|---|
| Charts | |
| Line chart | 75,000 rows |
| Area chart Normalized stacked area chart |
75,000 rows |
| Column chart Normalized column chart |
75,000 rows |
| Bar chart Normalized bar chart |
75,000 rows |
| Scatter chart | 75,000 rows |
| Pie chart | 1,000 rows |
| Tree chart | 1,000 rows |
| Tables | |
| Table | 100,000 rows |
| Pivot table | 100,000 cells |
| Pivot table | 800 columns |
| Geomaps | |
| Point map | 40,000 rows |
| Point map with clusters | 40,000 points |
| Choropleth map | 40,000 rows |
| Heat map | 40,000 rows |
| Polyline map | 40,000 rows |
Yandex DataSphere
Quotas
| Limit type | Value |
|---|---|
| Number of projects per community | 50 |
| Total dataset size per community | 1,024 GB |
| Number of datasets per community | 10 |
| Number of file storages per community | 10 |
| Number of Docker images per community | 3 |
| Project storage size (can be increased per project) | 10 GB |
| Number of communities linked to a single billing account | 100 |
| Number of communities per organization | 10 |
| VM usage restrictions | |
| c1.32 1 | 0 |
| c1.80 2 | 0 |
| g1.4 1 | 0 |
| g2.1 1 | 0 |
| g2.2 1 | 0 |
| g2.4 1 | 0 |
| g2.8 2 | 0 |
| gt4.1 1 | 0 |
1 To increase this quota, top up your billing account by at least ₽500 or create a request to support.
2 Quota increase is available for businesses only on a case-by-case basis.
Limits
| Limit type | Value |
|---|---|
| Maximum project storage size | 4,096 GB |
| Maximum dataset size | 4,096 GB |
| Number of datasets concurrently connected to a project | 3 |
| Maximum data size per job | 10 GB |
| Maximum size of each job file | 5 GB |
| Maximum size of each log file in a job | 100 MB |
| Total size of files available for download via DataSphere CLI | 1 GB |
| Maximum job data size per community | 10 TB |
Yandex Identity and Access Management
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of groups per organization | 100 |
| Maximum number of subjects from groups per organization | 1,000 |
| Maximum number of access bindings per organization | 2,000 |
| Maximum number of service accounts per cloud | 100 |
| Maximum number of API keys per cloud | 1,000 |
| Maximum number of authorized keys per cloud | 1,000 |
| Maximum number of static access keys per cloud | 1,000 |
Limits
There are no limits for Identity and Access Management.
Yandex IoT Core
Quotas
| Type of limit | Value |
|---|---|
| Number of registries per cloud | 10 |
| Number of devices per cloud | 1,000 |
| Number of brokers per cloud | 10 |
| Frequency of sending messages per broker | 50 per second |
| Number of clients concurrently connected to the broker | 50 |
Limits
| Type of limit | Value |
|---|---|
| Maximum size per message | 256 KB |
| Frequency of sending messages per device | No more than once per second |
| Maximum subtopic name length | 1,024 characters |
| Maximum number of aliases per device | 5 |
Note
Message delivery is not guaranteed if the limits are exceeded.
Other restrictions
- The
Retainflag is not supported. When using it, the MQTT broker saves the flagged message and sends it when you subscribe a device or registry to a topic next time. - Persistent sessions, when the MQTT broker saves information about a client (device or registry) to reconnect faster, are not supported.
- The
QoS 2: Exactly oncequality of service level for MQTT is not supported. - There is no guarantee that the devices or registries with the same ClientID cannot connect to the MQTT broker at the same time.
Yandex Key Management Service
Quotas
| Type of limit | Value |
|---|---|
| Number of symmetric keys | 100 |
| Number of asymmetric encryption keys | 100 |
| Number of asymmetric signature keys | 100 |
Limits
| Type of limit | Value |
|---|---|
| Number of versions per key | 100 |
| Maximum amount of data to encrypt with the encrypt operation | 32 KB |
Yandex Load Testing
There are no active quotas in Load Testing.
The computing resources consumed by agents are counted towards the quotas and subject to the Yandex Compute Cloud limits.
Yandex Lockbox
Quotas
| Limit type | Value |
|---|---|
| Maximum number of secrets per cloud | 10,000 |
Limits
| Type of limit | Value |
|---|---|
| Maximum total size of values in the key-value pairs of the secret version | 64 KB |
| Maximum number of versions per secret * | 1,000 |
* Deleted versions are ignored.
Yandex Managed Service for Apache Airflow™
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 5 |
| Total number of processor cores for all cluster components per cloud | 128 |
| Total virtual memory for all cluster components per cloud | 256 GB |
Limits
| Type of limit | Maximum value |
|---|---|
| Total number of processor cores for all cluster components | 104 |
| Total virtual memory for all cluster components | 416 GB |
| Total amount of data in the cluster metadata storage | 50 GB |
Yandex Managed Service for Apache Kafka®
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all broker hosts per cloud | 96 |
| Total virtual memory for all broker hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b2.medium (2 × 50% vCPU Intel Cascade Lake, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of brokers per cluster when using an HDD or SSD network storage, or an ultra high-speed network storage with three replicas (SSD) | 1 | 36 |
| Number of brokers in a cluster when using non-replicated or local SSDs | 3 | 36 |
| Amount of data on the broker when using SSD network storage | 10 GB | 4,096 GB |
| Amount of data on the broker when using HDD network storage | 10 GB | 2048 GB |
| Amount of data per broker when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 8,184 GB |
| Amount of data on the broker when using local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data on the broker when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
Yandex Managed Service for ClickHouse®
Quotas
| Type of limitation | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limitation | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of ClickHouse® hosts per non-sharded cluster when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) | 1 | 7 |
| Number of ClickHouse® hosts in a non-sharded cluster when using non-replicated SSD storage | 3 | 7 |
| Number of ClickHouse® hosts in a non-sharded cluster when using local SSD storage | 2 | 7 |
| Number of shards in a sharded cluster | 1 | 50 |
| Number of hosts per shard when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) | 1 | 7 |
| Number of hosts in a shard when using non-replicated SSD storage | 3 | 7 |
| Number of hosts in a shard when using local SSD storage | 2 | 7 |
| Total number of hosts per cluster | 1 | 353 (50 shards × 7 hosts + 3 ZooKeeper hosts) |
| Amount of data per host when using network HDD or SSD storage (for Intel Broadwell and Intel Cascade Lake) | 10 GB | 4,096 GB |
| Amount of data per host when using network HDD or SSD storage (for Intel Ice Lake) | 10 GB | 8,192 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 16,368 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
| Number of databases per cluster | 1 | 1000 |
Limits on the maximum number of objects
The limits on the maximum number of objects in a cluster have two threshold values:
-
Soft limit: When reached, the
system.warningssystem table will display a warning. -
Hard limit: When reached, creating new objects of this type will end with an error message.
Note
The hard limit threshold only works in ClickHouse® 25.2 and higher.
| Type of limitation | Soft limit | Hard limit |
|---|---|---|
| Number of databases | 500 | 1000 |
| Number of tables | 5000 | 10000 |
| Number of views | 5000 | 10000 |
| Number of external dictionaries | 500 | 1000 |
All limits are implemented based on ClickHouse® server settings. You cannot change them.
Yandex Managed Service for GitLab
Quotas
| Type of limit | Value |
|---|---|
| Number of instances per cloud | 5 |
| Disk size | 500 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | s2.micro (2 vCPU, 8 GB RAM) | s2.large (16 vCPU, 64 GB RAM) |
| Disk size | 30 GB | 500 GB |
Yandex Managed Service for Greenplum®
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | s2.medium (8 vCPU Intel Cascade Lake, 32 GB RAM) | i3-c40-m320 (40 vCPU Intel Ice Lake, 320 GB RAM) |
| Number of master hosts in the cluster | 2 | 2 |
| Number of segment hosts in the cluster | 2 | 32 |
| Number of segments per host | 1 | 16 |
| Amount of data on the host when using HDD network storage | 10 GB | 2048 GB |
| Amount of data per host when using network SSD storage | 10 GB | 8,192 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 8,184 GB |
| Amount of data on the host when using local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
Yandex Managed Service for Kubernetes
Quotas
| Limit type | Value |
|---|---|
| Total number of vCPUs across all masters per cloud | 60 |
| Total amount of RAM across all masters per cloud | 240 GB |
| Total number of vCPUs across all nodes per cloud | 192 |
| Total amount of RAM across all nodes per cloud | 384 GB |
| Total disk storage capacity across all nodes per cloud | 32 TB |
| Maximum number of Kubernetes clusters per cloud | 8 |
| Maximum number of node groups per cloud | 32 |
| Maximum number of nodes per cloud | 160 |
| Maximum number of node groups per Kubernetes cluster | 16 |
| Maximum number of nodes per Kubernetes cluster | 32 |
Limits
| Limit type | Value |
|---|---|
| Maximum number of volumes connected to a single node | 56 |
Yandex Managed Service for MongoDB
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of shards per cluster | 1 | 10 |
| Number of hosts per shard when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) | 1 | 7 |
| Number of hosts in a shard when storing data on non-replicated or local SSDs* | 3 | 7 |
| Number of hosts per cluster | 1 or 3 hosts depending on the disk type; the cluster is created in an unsharded state. | 70 (10 shards, 7 hosts) |
| Amount of data on the host when using network HDD or SSD storage | 10 GB | 2048 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 2,232 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)* | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake)* | 368 GB | 2944 GB |
| Number of databases per cluster | 1 | 1000 |
* Read more on how platform selection affects available storage types.
The maximum available number of simultaneous connections to a single Managed Service for MongoDB cluster host depends on the amount of RAM on the host:
| Amount of RAM | Maximum number of connections |
|---|---|
| 2 GB | 2048 |
| 4 GB | 4096 |
| 8 GB | 8192 |
| 16 GB or higher | 16 384 |
Yandex Managed Service for MySQL®
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Cascade Lake, 640 GB RAM) |
| Number of hosts per cluster when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) | 1 | 7 |
| Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 7 |
| Amount of data per host when using network SSD storage | 10 GB | 6,144 GB |
| Amount of data per host when using network HDD storage | 10 GB | 2,048 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 8,184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
| Number of databases per cluster | 1 | 1000 |
Yandex Managed Service for OpenSearch
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all hosts per cloud | 96 |
| Total virtual memory for all hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b2.medium (2 vCPU Intel Cascade Lake, 4 GB RAM, 50% vCPU) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM, 100% vCPU) |
Number of OPENSEARCH type host groups |
1 | 10 |
Number of hosts per OPENSEARCH type group when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) |
1 | 10 |
Number of hosts per OPENSEARCH type group when using non-replicated or local SSD storage |
3 | 10 |
Number of DASHBOARDS type host groups |
1 | 1 |
Number of hosts per DASHBOARDS type group |
1 | 2 |
| Amount of data on the host when using network HDD or SSD storage | 16 GB | 4,096 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 8,184 GB |
| Amount of data on the host when using local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
Yandex Managed Service for PostgreSQL
Quotas
| Type of limit | Value |
|---|---|
| Connection time-to-live | 12 hours |
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of hosts per cluster when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) | 1 | 16 |
| Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 16 |
| Amount of data per host when using network SSD storage | 10 GB | 4,096 GB |
| Amount of data per host when using network HDD storage | 10 GB | 2048 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 10,230 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
| Connections per user | 1 | 15,985 |
| Number of databases per cluster | 1 | 1000 |
Yandex Managed Service for Valkey™
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 64 |
| Total virtual memory for all database hosts per cloud | 512 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b2.medium (burstable, 4 GB RAM) |
hm3-c20-m320 (20 vCPUs, Intel Ice Lake, 320 GB RAM) |
| Number of hosts per unsharded cluster | 1 or 3 depending on the disk type | 7 |
| Number of shards in a sharded cluster | 1 | 10 |
| Number of hosts per shard when using an HDD or SSD network storage, or an ultra high-speed network storage with three replicas (SSD) | 1 | 7 |
| Number of hosts per shard when using local SSD storage* | 2 | 7 |
| Number of hosts per shard when using non-replicated SSD storage* | 3 | 7 |
| Number of hosts per sharded cluster | 1, 2, or 3 hosts depending on the disk type | 70 (10 shards, 7 hosts) |
| Amount of data per host when using network SSD storage | Twice the selected amount of RAM | 4,096 GB |
| Amount of data per host when using a non-replicated SSD storage* or an ultra high-speed network storage with three replicas (SSD) | Twice the selected amount of RAM but at least 93 GB | 8,184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)* | Twice the selected amount of RAM but at least 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake)* | Twice the selected amount of RAM but at least 368 GB | 2944 GB |
| Number of cluster connections | — | 65 000 |
* Read more on how platform selection affects available storage types.
Yandex Managed Service for YDB
Quotas
Dedicated instance mode
| Type of limit | Default value |
|---|---|
| Total number of processor cores for all database hosts per cloud | 64 |
| Total virtual memory for all database hosts per cloud | 256 GB |
| Maximum number of hosts per cloud | 8 |
| Maximum number of databases per cloud | 4 |
| Maximum number of storage groups per cloud | 8 |
Serverless mode
| Type of limit | Default value |
|---|---|
| Maximum number of databases | 4 |
| Maximum number of serverless queries per second, per cloud | 1,000 RUs |
| Maximum number of schema operations* per day, per serverless database | 1,000 |
| Maximum number of schema operations* per minute, per serverless database | 30 |
| Total storage size of serverless databases | 300 GB |
| Number of Data Streams shards in a serverless database | 100 |
*Transactions with quotas: creating, updating, and deleting table schemas, getting a table description, getting a list of tables, and creating and deleting directories.
Yandex Message Queue
Quotas
Messages
| Type of limit | Value |
|---|---|
Number of SendMessage and SendMessageBatch calls per queue |
300 calls per second for a standard queue |
Number of ReceiveMessage calls per queue |
300 calls per second for a standard queue |
Number of DeleteMessage and DeleteMessageBatch calls per queue |
300 calls per second for a standard queue |
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue |
300 calls per second for a standard queue |
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 | 1,000 |
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 |
| Rate of enqueueing messages in a FIFO queue | 100 messages per second |
| Queue name | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores. The name of a FIFO queue must end with the .fifo suffix. |
Messages
| Type of limit | Value |
|---|---|
Number of SendMessage and SendMessageBatch calls per queue |
30 calls per second for a FIFO queue |
Number of ReceiveMessage calls per queue |
30 calls per second for a FIFO queue |
Number of DeleteMessage and DeleteMessageBatch calls per queue |
30 calls per second for a FIFO queue |
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue |
30 calls per second for a FIFO queue |
| Batch entry ID | Maximum of 80 characters, including numbers, lowercase and uppercase 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:
|
| Maximum period for retaining messages in a queue | 1,209,600 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 | 262,144 bytes (256 KB) |
| Minimum message size | 1 byte |
| Maximum message visibility timeout | 12 hours |
| Minimum message visibility timeout | 0 seconds |
Maximum client message wait time in an empty queue (WaitTimeSeconds parameter) |
20 seconds |
Yandex MetaData Hub
Connection Manager quotas
| Quota | Value |
|---|---|
| Total number of connections per cloud | 1,000 |
Metastore quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 5 |
Schema Registry quotas
| Quota | Value |
|---|---|
| Total number of namespaces per cloud | 32 |
| Total number of schemas per cloud | 10 240 |
There are no limits for Yandex MetaData Hub.
Yandex Monitoring
Quotas
| Limit type | Value |
|---|---|
| Number of alerts per cloud | 1,000 |
| Number of metrics per service in the folder | 1,000,000 |
General limits
| Limit type | Value |
|---|---|
| Number of labels per metric (including required ones) |
16 |
| Number of values per label | 1,000 |
API limits
| Limit type | Value |
|---|---|
| Maximum number of metrics returned in the data export API request | 500 |
| Maximum number of metrics sent in the data import API request | 10,000 |
| Minimum number of samples returned in the data export API request | 10 |
| Maximum number of samples returned in the data export API request | 10,000 |
| Minimum time interval for exporting metrics | 1 second |
Alerting limits
| Limit type | Value |
|---|---|
| Number of metrics per alert | 100 |
| Number of SMS per number per day | 100 |
Yandex Network Load Balancer
Quotas
| Type of limitation | Value |
|---|---|
| Number of load balancers per cloud | 2 |
| Number of target groups per cloud | 100 |
Limits
| Type of limitation | Value |
|---|---|
| Number of targets per target group | 254 |
| Number of ports per listener | 10 |
| Number of health checks per attached target group | 1 |
| Health check protocol | TCP, HTTP |
Other restrictions
A single target group can only contain targets from a single cloud network.
Within a single availability zone, a target group can only include targets on the same subnet.
If you add a target to the internal load balancer's target group, it will not be directly accessible on the target port.
You can create a load balancer without a listener.
Health check traffic comes from the 198.18.235.0/24 and 198.18.248.0/24 ranges.
When adding targets for a load balancer, keep in mind the limit on the maximum number of concurrent TCP/UDP connections per VM.
Yandex Object Storage
Quotas
| Type of limit | Value |
|---|---|
| Storage volume per cloud | 1 TB |
| Number of buckets per cloud | 25 |
Limits
| Type of limit | Value |
|---|---|
| Maximum object size | 5 TB |
| Total header size per request to HTTP API | 8 KB |
| Size of user-defined metadata in an object | 2 KB |
| Maximum size of data to upload per request | 5 GB |
| Minimum size of data parts for multipart upload, except the last one | 5 MB |
| Maximum number of parts in multipart upload | 10,000 |
| Maximum bucket access policy size | 20 KB |
Yandex Query
Limits
| Type of limit | Value |
|---|---|
| Maximum query result retention time | 24 hours |
| Maximum streaming query runtime (preview stage) | 7 days |
| Maximum analytical query duration | 24 hours |
| Maximum query execution results size | 20 MB |
Quotas
| Type of limit | Value |
|---|---|
| Number of concurrent analytical queries | 100 |
| Number of concurrent streaming queries | 100 |
| Maximum analytical query duration | 30 minutes |
Warning
The maximum streaming query runtime (preview stage) is 7 days. Once expired, the query is forced to stop. To run streaming queries for an unlimited time, contact Yandex Cloud support.
Yandex Resource Manager
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of clouds per organization | 5 |
| Maximum number of folders per cloud | 50 |
Limits
There are no limits for the Resource Manager service.
Yandex Search API
Quotas
| Limit type | Value |
|---|---|
| API v1 | |
| Number of synchronous requests per day | 100,000Daily limit resets at 00:00:00 GMT (00:03:00 UTC+3) |
Number of synchronous requests per hour (hourly_limits) |
It depends on the time of day1From 00:00:00 to 00:59:59: 30% of the daily quotaFrom 00:59:59 to 03:59:59: 40% of the daily quotaFrom 04:00:00 to 07:59:59: 60% of the daily quotaFrom 08:00:00 to 08:59:59: 40% of the daily quota From 09:00:00 to 09:59:59: 30% of the daily quota From 10:00:00 to 10:59:59: 20% of the daily quota From 11:00:00 to 22:59:59: 10% of the daily quota From 23:00:00 to 23:59:59: 20% of the daily quota |
Number of synchronous requests per second (rps_restriction) |
Depends on the number of requests per hour: rps_restriction = hourly_limits/3,420 |
| API v2 | |
| Number of synchronous requests per hour | 10,000 |
| Number of synchronous requests per second | 10 |
| Number of synchronous requests per second to get a generative response | 1 |
| Number of deferred requests per hour | 35,000 |
| Number of deferred requests per second | 10 |
| Number of requests, per second, for results of a deferred request | 10 |
1 The time zone is UTC+3.
For example, if the quota is 100,000 requests per day, you can send a maximum of 10,000 requests per hour from 11:00:00 to 22:59:59 (approximately 3 requests per second) and a maximum of 40,000 requests (approximately 11 requests per second) from 08:00:00 to 08:59:59.
If you increase your daily quota of requests to 200,000, you can send a maximum of 20,000 requests per hour from 11:00:00 to 22:59:59 (approximately six requests per second) and a maximum of 80,000 requests (approximately 22 requests per second) from 08:00:00 to 08:59:59.
Limits
| Limit type | Value |
|---|---|
| Number of results returned | Up to 250 |
| Maximum request length | 400 characters |
| Maximum number of words per request | 40 words |
| Minimum processing time for a request in deferred mode | 5 minutes |
Yandex Serverless Containers
Quotas
| Type of limit | Value |
|---|---|
| Number of containers per cloud | 10 |
| Number of triggers per cloud | 100 |
| Total volume of Docker images used in active container revisions | 20 GB |
| Number of container instances per availability zone | 10 |
| Number of concurrent requests to containers per availability zone | 10 |
| Total RAM for all running container instances per availability zone | 20 GB |
| Total number of CPUs of all running container instances per availability zone | 10 |
| Number of provisioned container instances per cloud | 2 |
Limits
| Type of limit | Value |
|---|---|
| Maximum size of the container image | 10 GB |
| Maximum RAM per container instance | 8 GB |
| Maximum size of an HTTP request to the container, including HTTP headers and the request body | 3.5 MB |
| Maximum size of the container HTTP response, including HTTP headers and the response body | 3.5 MB |
| Maximum size of temporary files | 512 MB |
| Maximum time for request processing by the container before timeout, including the first launch initialization1 | 1 hour |
| Maximum total environment variable storage, including variable names2 | 4 KB |
| Maximum number of triggers per message queue | 1 |
| Maximum message size per trigger3 | 230 KB |
| Number of user networks per cloud | 1 |
1 A timeout of over 10 minutes is only available for long-lived containers.
2 Lockbox secrets are provided via environment variables and are also counted towards this limit.
3 The message may include service metadata, which will reduce the maximum message size.
Yandex SmartCaptcha
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of CAPTCHAs per cloud | 10 |
| Maximum number of challenge options per cloud | 32 |
| Maximum number of show rules per cloud | 250 |
Limits
There are no limits for SmartCaptcha.
Yandex Smart Web Security
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of security profiles per cloud | 5 |
| Maximum number of ARL profiles per cloud | 5 |
| Maximum number of WAF profiles per cloud | 10 |
| Maximum total number of security profile rules per cloud | 250 |
| Maximum total number of WAF exclusion rules per cloud | 250 |
| Maximum total number of ARL profile rules per cloud | 250 |
| Maximum total number of IP address mapping conditions per cloud | 2,500 |
Limits
| Type of limit | Value |
|---|---|
Maximum number of HTTP header conditions per rule |
20 |
Maximum number of Query Match conditions per rule |
20 |
| Maximum number of IP addresses, prefixes, or IP address ranges per condition | 10,000 |
Maximum number of HTTP method conditions per rule |
20 |
Maximum number of Host conditions per rule |
20 |
| Maximum length of a string in a regular expression | 255 characters |
| Maximum number of requests per second (RPS) in total for all load balancer virtual hosts connected to the same security profile1 |
20,000 |
1 If you expect more requests per second, contact your Yandex Cloud account manager.
Yandex SpeechKit
Quotas
| Type of limitation | Value |
|---|---|
| Streaming speech recognition | |
| Requests per second | 40 |
| Synchronous recognition | |
| Requests per second | 20 |
| Asynchronous recognition | |
| Recognition requests per hour | 500 |
| Operation status check requests via API v2 per hour | 2,500 |
| Operation status check requests via API v3 per second | 5 |
| Billable hours of audio per day1 | 10,000 |
| Speech synthesis | |
| Requests per second | 40 |
1 The first recognition request triggers the start of the time count.
Limits
| Type of limitation | Value |
|---|---|
| Streaming speech recognition | |
| Maximum duration of transmitted audio for entire session | 5 minutes |
| Maximum size of transmitted audio data | 10 MB |
| Maximum number of audio channels | 1 |
| Synchronous recognition | |
| Maximum file size | 1 MB |
| Maximum duration of audio | 30 seconds |
| Maximum number of audio channels | 1 |
| Asynchronous recognition | |
| Maximum file size when uploading to a bucket | 1 GB |
| Maximum file size when uploading in an API v3 request body | 60 MB |
| Maximum duration of audio | 4 hours |
| Period for storing recognition results on the server | 3 days |
| Speech synthesis | |
| Minimum duration of a pattern for synthesis | 1 second |
| Maximum request size for the API v1 | 5,000 characters |
| Maximum request size for the API v3 | 250 characters and 24 seconds |
| Maximum request size for the API v3 in unsafe mode | 5,000 characters |
Yandex SpeechSense
Quotas
| Type of limit | Value |
|---|---|
| Quotas for a project | |
| Number of dialogs you can get via the API, per second | 20 |
| Number of dialogs you can get via the API, per minute | 200 |
| Number of dialogs you can get via the API, per hour | 2,000 |
| Number of dialogs you can get via the API, per day | 20,000 |
Limits
| Type of limit | Value |
|---|---|
| User data storage period | 3 month |
| Calculation of updated and new tags per month | Once per night |
| Number of returned search results | 10,000 |
Yandex Translate
Quotas
| Type of limit | Value |
|---|---|
| Calls of one API method per second | 20 |
| Characters sent for translation or language detection, per hour | 1 million |
Limits
For limitations on the field values in the request body, see the API reference.
The limits for using glossaries are as follows:
-
The number of pairs sent to glossaries must be no more than 50.
-
The total number of Unicode characters in this structure must be no more than 20,000: 10,000 characters per source text and 10,000 characters per target text.
Warning
This only refers to texts without CGI parameters.
Yandex Virtual Private Cloud
Quotas
| Type of limit | Value |
|---|---|
| Number of cloud networks per cloud | 2 |
| Number of subnets per cloud | 6 |
| Number of all public IP addresses per cloud | 8 |
| Number of static public IP addresses per cloud | 2 |
| Number of routing tables per cloud | 8 |
| Number of static routes per cloud | 256 |
| Maximum number of security groups | 10 |
| Maximum number of security groups per interface | 5 |
Limits
| Type of limit | Value |
|---|---|
| Minimum CIDR size for a subnet | /28 |
| Maximum CIDR size for a subnet | /16 |
| Maximum number of VM connections when using custom security groups1 2 | 350,000 |
| Supported network and transport layer protocols | IP, ICMP, TCP, UDP, GRE, ESP, AH |
| Maximum number of rules per security group | 50 |
| Maximum number of CIDRs per rule | 50 |
| Size of the DNS server IP address list | 100 characters |
| Maximum number of DNS requests to a DNS server (second address in a subnet) | 1,000 requests per second |
| Maximum number of NAT gateways | 20 |
1 All TCP and UDP connections opened and half-opened within 180 seconds are taken into account. If there are no data or keep-alive packets in the connection during this time, it is forcibly closed.
2 The old network diagram had a limit of 50,000 connections.
Outgoing traffic filtering
Yandex Cloud automatically blocks traffic sent from Virtual Private Cloud public IP addresses to TCP port 25 of any servers on the internet and Yandex Compute Cloud VMs. The only exception is the traffic sent to Yandex Mail email servers, which is allowed and not blocked.
Yandex Cloud can provide a special public IP address with TCP port 25 opened upon request to the support team if you follow the Acceptable Use Policy. In case you violate the Policy, Yandex Cloud may block outgoing traffic on TCP port 25 again.
For public IP addresses that are already in use, port 25 cannot be opened.
Yandex Vision OCR
Quotas
| Type of limit | Value |
|---|---|
| Number of requests per second, synchronous mode | 1 |
| Number of requests per second, asynchronous mode | 10 |
| Number of requests per second, asynchronous mode (getting an operation status) | 50 |
| Number of requests per second, asynchronous mode (getting a response) | 50 |
Limits
| Type of limit | Value |
|---|---|
| Period for storing recognition results on the server | 3 days |
| Maximum file size for the OCR API | 10 MB |
| Maximum image size | 20 MP (length × width) |
| Maximum number of pages in a PDF file when using the OCR API in asynchronous mode | 200 |
Yandex WebSQL
| Limit | Value |
|---|---|
| Number of queries for ClickHouse® | 1 |
ClickHouse® is a registered trademark of ClickHouse, Inc.