[Yandex Cloud documentation](../index.md) > [Yandex Cloud Quota Manager](index.md) > Quota reference
# Yandex Cloud service quotas
Cloud Quota Manager allows you to manage quotas of your Yandex Cloud services using different interfaces.
This section contains quotas for services available in Quota Manager. Each table lists quota names and IDs you can use to manage quotas via Quota Manager. If the ID is not specified, you cannot use Quota Manager to view or update the quota.
The tables indicate the default quota values, which are the same as the [trial period](../getting-started/free-trial/concepts/quickstart.md) quotas. The limits apply to all [cloud](../resource-manager/concepts/resources-hierarchy.md#cloud) resources, unless otherwise specified.
## Yandex API Gateway {#api-gw}
API Gateway, Cloud Functions, and Serverless Containers share the same quota for the `Number of triggers per cloud ` (`serverless.triggers.count`). This quota is listed together with [Cloud Functions quotas](#sf).
## Yandex Application Load Balancer {#alb}
Service: `alb`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limitation | Value ||
|| Maximum number of load balancers per cloud
`apploadbalancer.loadBalancers.count` | 4 ||
|| Maximum number of HTTP routers per cloud
`apploadbalancer.httpRouters.count` | 16 ||
|| Maximum number of backend groups per cloud
`apploadbalancer.backendGroups.count` | 32 ||
|| Maximum number of target groups per cloud
`apploadbalancer.targetGroups.count` | 32 ||
|#
#### Limits {#limits}
Type of limit | 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 {#at}
Service: `audit-trails`, resource type: `resource-manager.cloud`.
#### Quotas {#audit-trails-quotas}
#|
|| Type of limitation | Value ||
|| Maximum number of trails per cloud
`audit-trails.trails.count` | 3 ||
|#
## Yandex BareMetal {#baremetal}
Service: `baremetal`, resource type: `resource-manager.cloud`.
#### Quotas {#baremetal-quotas}
#|
|| Type of limit | Value ||
|| Number of [servers](../baremetal/concepts/servers.md)
`baremetal.servers.count` for businesses | 5 ||
|| Number of servers
`baremetal.servers.count` for individuals^1^ | 2 ||
|| Number of [custom-configured](../baremetal/concepts/server-custom-configurations.md) servers in a build process per cloud
`baremetal.assemblingServers.count` | 0 ||
|| Number of [VRFs](../baremetal/concepts/private-network.md#vrf-segment)
`baremetal.vrfs.count` | 20 ||
|| Number of images
`baremetal.images.count` | 10 ||
|| Number of [private subnets](../baremetal/concepts/private-network.md#private-subnet)
`baremetal.privateSubnets.count` | 2 ||
|| Number of private subnets per server interface
`baremetal.privateSubnetsPerServerInterface.count` | 1 ||
|| Number of [dedicated public subnets](../baremetal/concepts/public-network.md#public-subnet)
`baremetal.dedicatedPublicSubnets.count` | 1 ||
|| Number of pools in dedicated public subnets
`baremetal.dedicatedPublicSubnetsHardwarePools.count` | 1 ||
|| Number of all static routes in a cloud
`baremetal.staticRoutes.count` | 10 ||
|#
^1^ This quota is defined automatically. Contact [support](https://center.yandex.cloud/support) to increase your quota.
## Yandex Certificate Manager {#certificate-manager}
Service: `certificate-manager`, resource type: `resource-manager.cloud`.
#### Quotas {#certificate-manager-quotas}
#|
|| Type of limit | Value ||
|| Number of certificates per cloud
`certificate-manager.certificates.count` | 20 ||
|| Number of domains per cloud
`certificate-manager.domains.count` | 10 ||
|#
#### Limits for Let's Encrypt® certificates {#certificate-manager-limits}
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
#### Useful links {#certificate-manager-see-also}
- [Let's Encrypt documentation: Limits](https://letsencrypt.org/ru/docs/rate-limits/)
## Yandex Cloud Backup {#backup}
Service: `backup`, resource type: `resource-manager.cloud`.
#### Quotas {#backup-quotas}
#|
|| Type of limit | Value ||
|| Number of virtual machines connected to Cloud Backup per cloud^1^
`backup.vms.count` | 50 ||
|| Number of BareMetal servers connected to Cloud Backup per cloud^1^
`backup.bmservers.count` | 20 ||
|| Total size of backups per cloud
`backup.storage.size` | 10 TB ||
|#
^1^ A virtual machine or BareMetal server is considered connected to Cloud Backup if it is associated with at least one [backup policy](../backup/concepts/policy.md). If the quota is exceeded, you will not be able to associate new VMs and BareMetal servers with backup policies.
## Yandex Cloud CDN {#cdn}
Service: `cdn`, resource type: `resource-manager.cloud`.
#### Quotas {#cdn-quotas}
#|
|| Type of limit | Value ||
|| Number of [CDN resources](../cdn/concepts/resource.md) per cloud
`cdn.resources.count` | 20 ||
|#
#### Limits {#cdn-limits}
| Type of limit | Value |
| ----- | ----- |
| Number of [cache purging](../cdn/concepts/caching.md#purge) requests per minute | 1 |
| Number of file paths per cache purging request | 10 |
| Number of [forced file caching](../cdn/concepts/caching.md#prefetch) requests per minute | 1 |
| Number of paths to files forcibly loaded into the cache per request | 100 |
| Number of IP addresses (subnet prefixes) in the IP-based access policy [list](../cdn/concepts/ip-address-acl.md#ip-list) | 100 |
| Number of [dedicated IP addresses](../cdn/concepts/dedicated-ip-addressing.md) for CDN resources per [billing account](../billing/concepts/billing-account.md) | 1 |
## Yandex Cloud Desktop {#cloud-desktop}
Service: `cloud-desktop`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Maximum number of desktops per cloud
`vdi.desktops.count` | 10 ||
|| Maximum number of desktop images per cloud
`vdi.desktopImages.count` | 8 ||
|| Maximum total size of desktop images per cloud
`vdi.desktopImages.size` | 1 TB ||
|| Maximum total number of vCPUs per cloud
`vdi.desktopCores.count` | 40 ||
|| Maximum total amount of RAM per cloud
`vdi.desktopMemory.size` | 80 GB ||
|| Maximum total HDD space per cloud
`vdi.hddDisks.size` | 600 GB ||
|| Maximum total SSD space per cloud
`vdi.ssdDisks.size` | 600 GB ||
|#
## Yandex Cloud DNS {#dns}
Service: `dns`, resource type: `resource-manager.cloud`.
#### Quotas {#cloud-dns-quotas}
#|
|| Type of limitation | Value ||
|| Number of zones per cloud
`dns.zones.count` | 100 ||
|| Number of record sets per cloud
`dns.recordSets.count` | 1,000 ||
|| Number of record sets per zone
`dns.recordSetsPerZone.count`| 100 ||
|#
#### Limits {#cloud-dns-limits}
Type of limitation | Value
----- | -----
Maximum number of records per record set | 100
Maximum number of concurrent record set updates | 1,000
Maximum number of networks per zone | 50
## Yandex Cloud Functions {#sf}
Service: `serverless-functions`, resource type: `resource-manager.cloud`.
#### Quotas {#functions-quotas}
#|
|| Type of limit | Value ||
|| Number of [triggers](../functions/concepts/trigger/index.md) per cloud^1^
`serverless.triggers.count` | 100 ||
|| Number of functions per cloud
`serverless.functions.count` | 10 ||
|| Number of tags per function
`serverless.functionTags.count` | 10 ||
|| Number of concurrent function calls (for all functions in each availability zone)
`serverless.request.count` | 10 ||
|| Number of function instances per availability zone
`serverless.workers.count` | 10 ||
|| Total RAM for all running functions per availability zone
`serverless.memory.size` | 20 GB ||
|| Number of [provisioned function instances](../functions/concepts/function.md#provisioned-instances) per cloud
`serverless.workersProvisioned.count` | 2 ||
|| Number of concurrent operations on a single function and its versions
`serverless.concurrentFunctionOperations.count` | 10 ||
|| Number of concurrent operations on all functions and their versions per folder
`serverless.concurrentFolderOperations.count` | 15 ||
|| Number of concurrent operations on all functions and their versions per cloud
`serverless.concurrentCloudOperations.count` | 20 ||
|| Number of [user networks](../functions/concepts/networking.md#user-network) per cloud | 10 ||
|#
^1^ API Gateway, Cloud Functions, and Serverless Containers share the same `Number of triggers per cloud` quota. The [management console](https://console.yandex.cloud/cloud?section=quotas) shows it as part of the Cloud Functions quota list.
For more information on the relationship between quotas, see [this section](../functions/concepts/limits.md#related-quotas).
#### Limits {#functions-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](../functions/concepts/function-invoke.md#request) and [response](../functions/concepts/function-invoke.md#response) | 3.5 MB
Maximum size of [temporary files](../functions/concepts/runtime/environment-variables.md#files) | 512 MB
Maximum function execution time before [timeout](../functions/operations/function/version-manage.md), including first call initialization^1^ | 1 hour
Maximum RAM per function instance | 8 GB
Maximum total size of environment variables, including their names^2^ | 4 KB
Maximum number of triggers per [message queue](../message-queue/concepts/queue.md) | 1
Maximum message size per trigger^3^ | 230 KB
Number of network packets per second per function instance | 10,000
^1^ A timeout longer than ten minutes is only available for [long-lived functions](../functions/concepts/long-lived-functions.md).
^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 {#functions-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](../functions/operations/function/version-manage.md).
## Yandex Cloud Logging {#logging}
Service: `logging`, resource type: `resource-manager.cloud`.
#### Quotas {#logging-quotas}
#|
|| Type of limitation | Value ||
|| Number of custom log groups per cloud
`logging.groups.count` | 10 ||
|| Maximum write speed
`logging.write.rate` | 1,000 records per second ||
|| Maximum record retention period
`logging.retentionDays.count` | 31 days ||
|#
There is no guarantee that records will be deleted as soon as the specified retention period expires: deletion may occur later.
#### Limits {#logging-limits}
Type of limitation | 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](../logging/concepts/filter.md#how-to) length | 1,000 characters
## Yandex Cloud Postbox {#postbox}
Service: `postbox`, resource type: `resource-manager.cloud`.
#### Quotas {#postbox-quotas}
#|
|| Type of limit | Value ||
|| Maximum number of recipients per email
`postbox.recipients_per_email.count` | 50 ||
|| Maximum size of an email with attachments
`postbox.email.size` | 10 MB ||
|| Maximum number of addresses
`postbox.identities.count` | 10 ||
|| Maximum email send rate
`postbox.send.rate` | 1 email per second ||
|| Maximum number of emails that can be sent within a 24-hour time interval
`postbox.emails_sent.count` | 200 ||
|| Maximum number of [configurations](../postbox/concepts/glossary.md#configuration)
`postbox.configuration_sets.count` | 5 ||
|#
## Yandex Compute Cloud {#compute}
Service: `compute`, resource type: `resource-manager.cloud`.
## Quotas {#compute-quotas}
### Quotas for instances and instance groups {#vm-quotas}
#|
|| Type of limit | Value ||
|| Number of [virtual machines](../compute/concepts/vm.md) per [cloud](../resource-manager/concepts/resources-hierarchy.md#cloud)
`compute.instances.count` | 12 ||
|| Total virtual memory across all VMs and number of available slots in [reserved instance pools](../compute/concepts/reserved-pools.md) per cloud
`compute.instanceMemory.size` | 128 GB ||
|| Number of [instance groups](../compute/concepts/instance-groups/index.md) per cloud
`compute.instanceGroups.count` | 10 ||
|| Maximum number of [VM placement groups](../compute/concepts/placement-groups.md) per cloud
`compute.placementGroups.count` | 2 ||
|| Maximum number of VMs per partition in a VM placement group with the [partition placement](../compute/concepts/placement-groups.md#partition) strategy | 100 ||
|| Maximum number of [security groups](../vpc/concepts/security-groups.md) per [network interface](../compute/concepts/network.md)
{% note warning %}
You can increase this quota only upon agreement with your account manager.
{% endnote %}
| 5 ||
|#
### vCPU quotas {#vcpu-quotas}
#|
|| Type of limit | Value ||
|| Total number of [vCPUs](../compute/concepts/performance-levels.md) across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceCores.count` | 32 ||
|| Total number of Intel Ice Lake Compute-Optimized vCPUs across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceHighFreqCores.count` | 0 ||
|#
### GPU quotas {#gpu-quotas}
#|
|| Type of limit | Value ||
|| Total number of NVIDIA® Tesla® V100 [GPUs](../compute/concepts/gpus.md) across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceGpus.count` | 0 ||
|| Total number of AMD EPYC™ with NVIDIA® Ampere® A100 GPUs across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceA100Gpus.count` | 0 ||
|| Total number of Gen2 GPUs across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceV3IGpus.count` | 0 ||
|| Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceT4Gpus.count` | 0 ||
|| Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs and number of available slots in reserved instance pools per cloud in the `ru-central1-d` availability zone
`compute.instanceT4Gpus.count.ru-central1-d` | 0 ||
|| Total number of Intel Ice Lake with T4i GPUs across all VMs and number of available slots in reserved instance pools per cloud
`compute.instanceT4IGpus.count` | 0 ||
|#
### Disk quotas {#disk-quotas}
#|
|| Type of limit | Value ||
|| Total number of [disks](../compute/concepts/disk.md) per cloud
`compute.disks.count` | 32 ||
|| Total [HDD storage](../compute/concepts/disk.md#disks-types) capacity per cloud
`compute.hddDisks.size` | 500 GB ||
|| Total SSD storage capacity per cloud
`compute.ssdDisks.size` | 200 GB ||
|| Total non-replicated SSD storage capacity per cloud
`compute.ssdNonReplicatedDisks.size` | 558 GB ||
|| Total capacity of ultra high-speed network SSD storages with three replicas per cloud
`compute.ssdIOM3Disks.size` | 186 GB ||
|| Number of [non-replicated disk placement groups](../compute/concepts/disk-placement-group.md) per cloud
`compute.diskPlacementGroups.count` | 5 ||
|#
### File storage quotas {#fs-quotas}
#|
|| Type of limit | Value ||
|| Total number of [file storages](../compute/concepts/filesystem.md) per cloud
`compute.filesystems.count` | 100 ||
|| Total [HDD](../compute/concepts/filesystem.md#types) file storage size per cloud
`compute.hddFilesystems.size` | 512 GB ||
|| Total SSD file storage size per cloud
`compute.ssdFilesystems.size` | 512 GB ||
|#
### Image quotas {#image-quotas}
#|
|| Type of limit | Value ||
|| Number of [images](../compute/concepts/image.md) per cloud
`compute.images.count` | 32 ||
|| Total volume of images per cloud
`compute.images.size` | 1,024 GB ||
|| Number of [images optimized for deployment](../compute/concepts/image.md#images-optimized-for-deployment) per cloud^1^
`compute.diskPools.count` | 0 ||
|#
{% note info %}
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](https://center.yandex.cloud/support) to increase these quotas.
{% endnote %}
### Snapshot quotas {#snapshot-quotas}
#|
|| Type of limit | Value ||
|| Total number of [disk snapshots](../compute/concepts/snapshot.md) per cloud
`compute.snapshots.count` | 32 ||
|| Total storage capacity of all disk snapshots per cloud
`compute.snapshots.size` | 400 GB ||
|| Number of [disk snapshot schedules](../compute/concepts/snapshot-schedule.md) per cloud
`compute.snapshotSchedules.count` | 32 ||
|#
### Dedicated host quotas {#dedicated-host-quotas}
#|
|| Type of limit | Value ||
|| Number of [dedicated hosts](../compute/concepts/dedicated-host.md) per dedicated host group^1^
`compute.dedicatedHosts.count` | 0 ||
|| Number of dedicated host groups per cloud
`compute.hostGroups.count` | 6 ||
|#
### Other quotas {#compute-other-quotas}
#|
|| Type of limit | Value ||
|| Number of concurrent [operations](../api-design-guide/concepts/operation.md) per [folder](../resource-manager/concepts/resources-hierarchy.md#folder) | 15 ||
|| Number of [reserved instance pools](../compute/concepts/reserved-pools.md) per cloud^1^
`compute.reservedInstancePools.count` | 1 ||
|#
^1^ To increase [quotas](https://console.yandex.cloud/cloud?section=quotas) for deployment-optimized images, dedicated hosts, or reserved instance pools, contact [support](https://center.yandex.cloud/support).
## Limits {#compute-limits}
### VM limits {#compute-limits-vm}
Limits per VM depend on the VM [platform](../compute/concepts/vm-platforms.md):
{% list tabs group=platforms %}
- Intel Broadwell {#broadwell}
#|
|| **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 VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 18 | 8 ||
|| ^ | ^ | Number of VCPUs > 18 | 16^3^ ||
|| ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 ||
|| ^ | ^ | Number of VCPUs >= 6 | 80 ||
|| Maximum number of [network interfaces](../compute/concepts/network.md) connected to a single VM | Bus topology
`PCI_TOPOLOGY_V1` | > | 8^3^ ||
|| ^ | `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](../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 ||
|#
- Intel Cascade Lake {#cascade}
#|
|| **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 VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 20 | 8 ||
|| ^ | ^ | Number of VCPUs > 20 | 16^3^ ||
|| ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 ||
|| ^ | ^ | Number of VCPUs >= 6 | 80 ||
|| Maximum number of [network interfaces](../compute/concepts/network.md) connected to a single VM | Bus topology
`PCI_TOPOLOGY_V1` | > | 8^3^ ||
|| ^ | `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](../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 ||
|#
- Intel Ice Lake {#ice}
#|
|| **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 VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 32 | 8 ||
|| ^ | ^ | Number of VCPUs > 32 | 16^3^ ||
|| ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 ||
|| ^ | ^ | Number of VCPUs >= 6 | 80 ||
|| Maximum number of [network interfaces](../compute/concepts/network.md) connected to a single VM | Bus topology
`PCI_TOPOLOGY_V1` | > | 8^3^ ||
|| ^ | `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](../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 ||
|#
- Intel Ice Lake (Compute Optimized) {#optimized}
#|
|| **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 VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 32 | 8 ||
|| ^ | ^ | Number of VCPUs > 32 | 16^3^ ||
|| ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 ||
|| ^ | ^ | Number of VCPUs >= 6 | 80 ||
|| Maximum number of [network interfaces](../compute/concepts/network.md) connected to a single VM | Bus topology
`PCI_TOPOLOGY_V1` | > | 8^3^ ||
|| ^ | `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](../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 ||
|#
{% endlist %}
^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.
{% note 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.
{% endnote %}
### VM limits on disk operations {#compute-limits-vm-disks}
{% list tabs group=disks %}
- Network SSD {#net-ssd}
Type of limit | Value
--- | ---
Maximum^4^ [IOPS](../compute/concepts/storage-read-write.md) per vCPU | 3,500
Maximum^5^ [bandwidth](../compute/concepts/storage-read-write.md) per vCPU | 45 MB/s
- Network HDD {#net-hdd}
Type of limit | Value
--- | ---
Maximum^4^ [IOPS](../compute/concepts/storage-read-write.md) per vCPU | 3,500
Maximum^5^ [bandwidth](../compute/concepts/storage-read-write.md) per vCPU | 45 MB/s
- Non-replicated SSD {#non-replicated-ssd}
Type of limit | Value
--- | ---
Total number of non-replicated SSDs per placement group | 8
Maximum^4^ [IOPS](../compute/concepts/storage-read-write.md) per vCPU | 10,000
Maximum^4^ IOPS per VM | 100,000
Maximum^5^ [bandwidth](../compute/concepts/storage-read-write.md) per vCPU | 100 MB/s
Maximum^5^ bandwidth per VM | 1 GB/s
- Ultra high-speed network storage with three replicas (SSD) {#high-perf-ssd}
Type of limit | Value
--- | ---
Maximum^4^ [IOPS](../compute/concepts/storage-read-write.md) per vCPU | 10,000
Maximum^4^ IOPS per VM | 100,000
Maximum^5^ [bandwidth](../compute/concepts/storage-read-write.md) per vCPU | 100 MB/s
Maximum^5^ bandwidth per VM | 1 GB/s
{% endlist %}
### Disk and file storage limits {#compute-limits-disks}
{% list tabs group=disks %}
- Network SSD {#net-ssd}
Type of limit | Value
--- | ---
Maximum disk size | 256 TB
[Allocation unit](../compute/concepts/storage-read-write.md) size | 32 GB
Maximum^4^ IOPS for writes per disk | 40,000
Maximum^4^ IOPS for writes per allocation unit | 1,000
Maximum^5^ bandwidth for writes per disk | 450 MB/s
Maximum^5^ bandwidth for writes per allocation unit | 15 MB/s
Maximum^4^ IOPS for reads per disk | 20,000
Maximum^4^ IOPS for reads per allocation unit | 1,000
Maximum^5^ bandwidth for reads per disk | 450 MB/s
Maximum^5^ bandwidth for reads per allocation unit | 15 MB/s
- Network HDD {#net-hdd}
Type of limit | Value
--- | ---
Maximum disk size | 256 TB
[Allocation unit](../compute/concepts/storage-read-write.md) size | 256 GB
Maximum^4^ IOPS for writes per disk | 11,000
Maximum^4^ IOPS for writes per allocation unit | 300
Maximum^5^ bandwidth for writes per disk | 240 MB/s
Maximum^5^ bandwidth for writes per allocation unit | 30 MB/s
Maximum^4^ IOPS for reads per disk | 2,000
Maximum^4^ IOPS for reads per allocation unit | 300
Maximum^5^ bandwidth for reads per disk | 240 MB/s
Maximum^5^ bandwidth for reads per allocation unit | 30 MB/s
- Non-replicated SSD {#non-replicated-ssd}
Type of limit | Value
--- | ---
Minimum non-replicated disk size | 93 GB
[Allocation unit](../compute/concepts/storage-read-write.md) size | 93 GB
Maximum^4^ IOPS for writes per disk | 75,000
Maximum^4^ IOPS for writes per allocation unit | 5,600
Maximum^5^ bandwidth for writes per disk | 1 GB/s
Maximum^5^ bandwidth for writes per allocation unit | 82 MB/s
Maximum^4^ IOPS for reads per disk | 75,000
Maximum^4^ IOPS for reads per allocation unit | 28,000
Maximum^5^ bandwidth for reads per disk | 1 GB/s
Maximum^5^ bandwidth for reads per allocation unit | 110 MB/s
- Ultra high-speed network storage with three replicas (SSD) {#high-perf-ssd}
Type of limit | Value
--- | ---
Minimum capacity of ultra high-speed network storage with three replicas (SSD) | 93 GB
[Allocation unit](../compute/concepts/storage-read-write.md) size | 93 GB
Maximum^4^ IOPS for writes per disk | 40,000
Maximum^4^ IOPS for writes per allocation unit | 5,600
Maximum^5^ bandwidth for writes per disk | 1 GB/s
Maximum^5^ bandwidth for writes per allocation unit | 82 MB/s
Maximum^4^ IOPS for reads per disk | 75,000
Maximum^4^ IOPS for reads per allocation unit | 28,000
Maximum^5^ bandwidth for reads per disk | 1 GB/s
Maximum^5^ bandwidth for reads per allocation unit | 110 MB/s
{% endlist %}
{% list tabs group=storages %}
- SSD storage {#ssd}
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
- HDD storage {#hdd}
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
{% endlist %}
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](../compute/concepts/storage-read-write.md).
^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 {#compute-limits-snapshot-schedule}
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 {#compute-other-limits}
Type of limit | Value
--- | ---
Time to complete processes when stopping a VM^6^ | 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 {#container-registry}
Service: `container-registry`, resource type: `resource-manager.cloud`.
#### Quotas {#container-registry-quotas}
#|
|| Type of limit | Value ||
|| Maximum number of [registries](../container-registry/concepts/registry.md) per [cloud](../resource-manager/concepts/resources-hierarchy.md#cloud)
`container-registry.registries.count` | 10 ||
|| Number of concurrent [Docker image](../container-registry/concepts/docker-image.md) [scans](../container-registry/concepts/vulnerability-scanner.md) running in a single cloud
`container-registry.parallelScans.count` | 10 ||
|#
#### Limits {#container-registry-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](../container-registry/concepts/repository.md) that can be checked by a trial run of the [Docker image lifecycle policy](../container-registry/concepts/lifecycle-policy.md) | 50 000
Maximum size of a Docker image to scan | 4 GB
Maximum number of Docker images to [scan](../container-registry/operations/scanning-docker-image.md) per request | 10 000
## Yandex Data Processing {#dataproc}
#### Quotas {#dataproc-quotas}
VMs that make up Yandex Data Processing clusters utilize your Yandex Compute Cloud cloud [quotas](https://console.yandex.cloud/cloud?section=quotas).
#### Limits {#dataproc-limits}
Type of limit | Value
--- | ---
Minimum host configuration | b2.medium (2 × [50%](../compute/concepts/performance-levels.md) vCPU Intel Cascade Lake, 4 GB RAM)
Maximum host configuration | m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 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`) | 262,074 GB
## Yandex Data Transfer {#data-transfer}
Service: `data-transfer`, resource type: `resource-manager.cloud`.
#### Quotas {#dataproc-quotas}
#|
|| Type of limitation | Value ||
|| Endpoints
`datatransfer.total_endpoints.count` | 100 ||
|| Transfers
`datatransfer.total_transfers.count` | 50 ||
|| Running transfers
`datatransfer.running_transfers.count` | 10 ||
|#
#### Limits {#dataproc-limits}
| Type of limitation | Value |
|----------------------------------|---------:|
| Endpoints | 400 |
| Transfers | 200 |
| Running transfers | 50 |
## Yandex Identity and Access Management {#iam}
Service: `iam`, resource type: `resource-manager.cloud`.
#### Quotas {#iam-quotas}
#|
|| Type of limitation | Value ||
|| Number of workload identity federations
`iam.oidcWLIFederations.count` | 50 ||
|| Number of service accounts linked to federations
`iam.saFederatedCredentials.count` | 200 ||
|| Maximum number of service accounts per cloud
`iam.serviceAccounts.count` | 100 ||
|| Maximum number of API keys per cloud
`iam.apiKeys.count` | 1,000 ||
|| Maximum number of authorized keys per cloud
`iam.authorizedKeys.count` | 1,000 ||
|| Maximum number of static access keys per cloud
`iam.accessKeys.count` | 1,000 ||
|#
#### Limits {#iam-limits}
There are no limits for Identity and Access Management.
## Yandex Identity Hub {#organization}
Service: `organization-manager`, resource type: `organization-manager.organization`.
#### Quotas {#organization-quotas}
#|
|| Type of limit | Value ||
|| Maximum number of subjects per organization
`organization-manager.memberships.count` | 10,000 ||
|| Maximum number of organizations a subject may belong to (quota for the subject) | 100 ||
|| Maximum number of invitations to an organization
`organization-manager.invites.count` | 100 ||
|| Maximum number of organizations a subject may create | 10 ||
|| Maximum number of federations per organization
`organization-manager.federations.count` | 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 {#organization-limits}
There are no limits for Yandex Identity Hub.
## Yandex IoT Core {#iot}
Service: `iot`, resource type: `resource-manager.cloud`.
#### Quotas {#iot-quotas}
#|
|| Type of limit | Value ||
|| Number of registries per cloud
`iot.registries.count` | 10 ||
|| Number of devices per cloud
`iot.devices.count`| 1,000 ||
|| Number of brokers per cloud
`iot.brokers.count` | 10 ||
|| Frequency of sending messages per broker
`iot.brokerMessaging.rate` | 50 per second ||
|| Number of clients concurrently connected to the broker
`iot.brokerConnections.count` | 50 ||
|#
#### Limits {#iot-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](../iot-core/concepts/topic/subtopic.md) name length | 1,024 characters
Maximum number of [aliases](../iot-core/concepts/topic/usage.md#aliases) per device | 5
{% note info %}
Message delivery is not guaranteed if the limits are exceeded.
{% endnote %}
#### Other restrictions {#iot-other-restrictions}
* The `Retain` flag is not supported. This flag enables the MQTT broker to save the flagged message and send it when subscribing to the 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 once` quality of service level for MQTT is not supported.
* There is no guarantee that the devices or registries with the same [ClientID](https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html#_Toc385349242) cannot connect to the MQTT broker at the same time.
## Yandex Key Management Service {#kms}
Service: `kms`, resource type: `resource-manager.cloud`.
#### Quotas {#kms-quotas}
#|
|| Type of limitation | Value ||
|| Number of [symmetric keys](../kms/concepts/key.md)
`kms.keys.count` | 100 ||
|| Number of asymmetric [encryption](../kms/concepts/asymmetric-encryption-key.md) keys
`kms.asymmetricEncryptionKeys.count` | 100 ||
|| Number of asymmetric [signature](../kms/concepts/asymmetric-signature-key.md) keys
`kms.asymmetricSignatureKeys.count`| 100 ||
|#
#### Limits {#kms-limits}
Type of limitation | Value
----- | -----
Number of versions per key | 100
Maximum amount of data to encrypt with the [encrypt](../kms/api-ref/SymmetricCrypto/encrypt.md) operation | 32 KB
## Yandex Lockbox {#lockbox}
Service: `lockbox`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limitation | Value ||
|| Maximum number of secrets per cloud
`lockbox.secrets.count`| 10,000 ||
|| Maximum number of versions per secret
`lockbox.versions.count` | 1,000 ||
|#
#### Limits {#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™ {#airflow}
Service: `managed-airflow`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`managed-airflow.clusters.count` | 5 ||
|| Total number of processor cores for all cluster components per cloud
`managed-airflow.cpu.count` | 128 ||
|| Total virtual memory for all cluster components per cloud
`managed-airflow.memory.size` | 256 GB ||
|#
#### Limits {#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® {#mkf}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#mkf-quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#mkf-limits}
| Type of limit | Minimum value | Maximum value |
|:---------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------|:-------------------------------------------------|
| Host class | b2.medium (2 × [50%](../compute/concepts/performance-levels.md) vCPUs, Intel Cascade Lake, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) |
| Number of brokers per cluster when using an HDD or SSD network storage or an ultra high-speed network SSD storage with three replicas | 1 | 32 |
| Number of brokers per cluster when using either a non-replicated or a local SSD storage | 1 | 32 |
| Amount of data per broker when using an SSD network storage | 10 GB | 32,768 GB |
| Amount of data per broker when using an HDD network storage | 10 GB | 2,048 GB |
| Amount of data per broker when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 8,184 GB |
| Amount of data per broker when using a local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per broker when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB |
## Yandex Managed Service for Apache Spark™ {#msp}
Service: `managed-spark`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`managed-spark.clusters.count` | 2 ||
|| Total number of processor cores for all hosts for drivers and executors per cloud
`managed-spark.cpu.count` | 128 ||
|| Total virtual memory for all hosts for drivers and executors per cloud
`managed-spark.memory.size` | 256 GB ||
|#
#### Limits {#limits}
| Type of limit | Minimum value | Maximum value |
|:----------------------------------------------|:-------------------------|:-------------------------------|
| Host class | c2-m8 (2 vCPUs, 8 GB RAM) | c32-m256 (32 vCPUs, 256 GB RAM) |
| Number of hosts for drivers per cluster | 0 | 100 |
| Number of hosts for executors per cluster | 0 | 100 |
## Yandex Managed Service for ClickHouse® {#mch}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#mch-quotas}
#|
|| **Type of limit** | **Value** ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#mch-limits}
#|
|| **Type of limit** | **Minimum value** | **Maximum value** ||
|| Host class | b1.medium (2 × [50%](../compute/concepts/performance-levels.md) vCPUs, Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 GB RAM) ||
|| Number of ClickHouse® hosts per non-sharded cluster when using a network HDD or SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 ||
|| Number of ClickHouse® hosts per non-sharded cluster when using a non-replicated SSD storage | 3 | 7 ||
|| Number of ClickHouse® hosts per non-sharded cluster when using a local SSD storage | 2 | 7 ||
|| Number of shards per sharded cluster | 1 | 100 ||
|| Number of hosts per shard when using a network HDD or SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 ||
|| Number of hosts per shard when using a non-replicated SSD storage | 3 | 7 ||
|| Number of hosts per shard when using a local SSD storage | 2 | 7 ||
|| Total number of hosts per cluster | 1 | 355 (50 shards × 7 hosts + 5 ZooKeeper hosts) ||
|| Amount of data per host when using a network HDD or SSD storage (for Intel Broadwell and Intel Cascade Lake) | 10 GB | 4,096 GB ||
|| Amount of data per host when using a network HDD or SSD storage (for Intel Ice Lake) | 10 GB | 8192 GB ||
|| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 16,368 GB ||
|| Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1500 GB ||
|| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB ||
|| Number of databases per cluster | 1 | 1000 ||
|#
#### Limits on the maximum number of objects {#mch-objects-limits}
The limits on the maximum number of objects per cluster have two threshold values:
* _Soft limit_: When reached, the `system.warnings` [system table](https://clickhouse.com/docs/enen/operations/system-tables/system_warnings) will display a warning.
* _Hard limit_: When reached, creating new objects of this type will end with an error message.
{% note info "Note" %}
The _hard limit_ threshold only works in ClickHouse® 25.2 and higher.
{% endnote %}
#|
|| **Type of limit** | **Soft limit** | **Hard limit** ||
|| Number of databases | 500 | 1,000 ||
|| Number of tables | 5,000 | 10,000 ||
|| Number of views | 5,000 | 10,000 ||
|| Number of external dictionaries | 500 | 1,000 ||
|#
All limits are implemented based on the [ClickHouse® server settings](https://clickhouse.com/docs/enen/operations/server-configuration-parameters/settings). You cannot change them.
## Yandex Managed Service for GitLab {#mgl}
Service: `managed-gitlab`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of instances per cloud
`managed-gitlab.instances.count` | 5 ||
|| Disk size | 500 GB ||
|| Number of managed runners per cloud
`managed-gitlab.runners.count` | 5 ||
|| Number of managed workers per cloud
`managed-gitlab.workers.count` | 10 ||
|#
#### Limits {#limits}
Type of limit | Minimum value | Maximum value
--- | --- | ---
Host class | s2.micro (2 vCPUs, 8 GB RAM) | s2.large (16 vCPUs, 64 GB RAM)
Disk size | 30 GB | 500 GB
## Yandex MPP Analytics for PostgreSQL {#mgp}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#limits}
| Type of limit | Minimum value | Maximum value |
|:--------------------------------------------------------------------------------------------------------------|:-------------------------------------------------|:-------------------------------------------------|
| Host class | s2.medium (8 vCPU Intel Cascade Lake, 32 GB RAM) | m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 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 an SSD network storage | 10 GB | 8,192 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 8,184 GB |
| Amount of data per host when using a local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB |
## Yandex Managed Service for Kubernetes {#managed-k8s}
Service: `managed-kubernetes`, resource type: `resource-manager.cloud`.
#### Quotas {#managed-k8s-quotas}
#|
|| **Type of limit** | **Value** ||
|| Total number of vCPUs across all masters per cloud
`managed-kubernetes.masterCores.count` | 60 ||
|| Total amount of RAM across all masters per cloud
`managed-kubernetes.masterMemory.size` | 240 GB ||
|| Total number of vCPUs across all nodes per cloud
`managed-kubernetes.cores.count` | 240 ||
|| Total amount of RAM across all nodes per cloud
`managed-kubernetes.memory.size` | 960 GB ||
|| Total disk storage capacity across all nodes per cloud
`managed-kubernetes.disk.size` | 30,000 GB ||
|| Maximum number of Kubernetes clusters per cloud
`managed-kubernetes.clusters.count` | 10 ||
|| Maximum number of node groups per cloud
`managed-kubernetes.nodeGroups.count` | 160 ||
|| Maximum number of nodes per cloud
`managed-kubernetes.nodes.count` | 160 ||
|| Maximum number of node groups per Kubernetes cluster
`managed-kubernetes.clusterNodeGroups.count` | 32 ||
|| Maximum number of nodes per node group
`managed-kubernetes.groupNodes.count` | 200 ||
|| Maximum number of nodes per Kubernetes cluster
`managed-kubernetes.clusterNodes.count` | 200 ||
|#
#### Limits {#managed-k8s-limits}
#|
|| **Type of limit** | **Value** ||
|| Maximum number of [volumes](../managed-kubernetes/concepts/volume.md) connected to a single node | 56 ||
|#
## Yandex Managed Service for MySQL® {#mmy}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#mmy-quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#mmy-limits}
| Type of limit | Minimum value | Maximum value |
|:------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------|:-----------------------------------------------------|
| Host class | b1.medium (2 × [50%](../compute/concepts/performance-levels.md) vCPUs, Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPU, AMD Zen 4, 1,792 GB RAM) |
| Number of hosts per cluster configured with either HDD/SSD network storage or an ultra high-speed SSD network storage with three replicas | 1 | 7 |
| Number of hosts per cluster configured with either non-replicated or local SSD storage | 3 | 7 |
| Amount of data per host with SSD network storage | 10 GB | 6,144 GB |
| Amount of data per host with HDD network storage | 10 GB | 2,048 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 8,184 GB |
| Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB |
## Yandex Managed Service for OpenSearch {#mos}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of processor cores for all hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#limits}
| Type of limit | Minimum value | Maximum value |
|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------|:------------------------------------------------------------|
| Host class | b2.medium (2 vCPUs Intel Cascade Lake, 4 GB RAM, 50% vCPU) | m4a-c224-m1792 (224 vCPUs AMD Zen 4, 1,792 GB RAM, 100% vCPU) |
| Number of `OPENSEARCH` host groups | 1 | 10 |
| Number of hosts per `OPENSEARCH` group when using a network HDD or SSD storage or an ultra high-speed network storage with three replicas (SSD) | 1 | 10 |
| Number of hosts per `OPENSEARCH` group when using a non-replicated or local SSD storage | 3 | 10 |
| Number of `DASHBOARDS` host groups | 1 | 1 |
| Number of hosts per `DASHBOARDS` group | 1 | 2 |
| Amount of data per host when using a 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 SSD storage with three replicas | 93 GB | 8,184 GB |
| Amount of data per host when using a local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB |
## Yandex Managed Service for PostgreSQL {#mpg}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#mpg-quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#mpg-limits}
| Type of limit | Minimum value | Maximum value |
|:------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------|:-------------------------------------------------|
| Host class | b1.medium (2 × [50%](../compute/concepts/performance-levels.md) vCPU Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) |
| Number of hosts per cluster configured with either HDD/SSD network storage or an ultra high-speed SSD network storage with three replicas | 1 | 16 |
| Number of hosts per cluster configured with either non-replicated or local SSD storage | 3 | 16 |
| Data volume per host with SSD network storage | 10 GB | 8,192 GB |
| Amount of data per host when using a network HDD storage (for Intel Broadwell) | 10 GB | 2,048 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas (for AMD Zen 4) | 93 GB | 16,368 GB |
| Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB |
| Connections per user | 1 | 15,985 |
| Number of databases per cluster | 1 | 1000 |
## Yandex Managed Service for Trino {#mtr}
Service: `managed-trino`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`managed-trino.clusters.count` | 10 ||
|| Total number of processor cores for all cluster components per cloud
`managed-trino.cpu.count` | 120 ||
|| Total virtual memory for all cluster components per cloud
`managed-trino.memory.size` | 480 GB ||
|#
#### Limits {#limits}
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Host class | c4-m16 (4 vCPUs, 16 GB RAM) | c8-m32 (8 vCPUs, 32 GB RAM) |
| Number of workers per cluster | 1 | 64 |
## Yandex Managed Service for Valkey™ {#mrd}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#mrd-quotas}
#|
|| **Type of limit** | **Value** ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#mrd-limits}
#|
|| **Type of limit** | **Minimum value** | **Maximum value** ||
|| Host class | b2.medium (`burstable`, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) ||
|| Number of hosts per unsharded cluster | 1 or 3 depending on the [disk type](../managed-valkey/concepts/storage.md#storage-type-selection) | 7 ||
|| Number of shards per sharded cluster | 1 | 10 ||
|| Number of hosts per shard when using a network SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 ||
|| Number of hosts per shard when using a local SSD storage^*^ | 2 | 7 ||
|| Number of hosts per shard when using a non-replicated SSD storage^*^ | 3 | 7 ||
|| Number of hosts per sharded cluster | 1, 2, or 3 hosts depending on the [disk type](../managed-valkey/concepts/storage.md#storage-type-selection) | 70 (10 shards × 7 hosts) ||
|| Amount of data per host when using an SSD network 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 SSD storage with three replicas | Twice the selected amount of RAM but at least 93 GB | 8,184 GB ||
|| Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | Twice the selected amount of RAM but at least 100 GB | 1,536 GB ||
|| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | Twice the selected amount of RAM but at least 368 GB | 5888 GB ||
|| Number of cluster connections | — | 65,000 ||
|#
^*^ Read more on how platform selection affects [available storage types](../managed-valkey/concepts/storage.md).
## Yandex Managed Service for YDB {#ydb}
Service: `ydb`, resource type: `resource-manager.cloud`.
#### Quotas {#ydb-quotas}
**Dedicated instance mode**
#|
|| Type of limit | Default value ||
|| Total number of CPU cores for all database hosts per cloud
`ydb.dedicatedComputeCores.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`ydb.dedicatedComputeMemory.size` | 256 GB ||
|| Maximum number of hosts per cloud
`ydb.dedicatedComputeNodes.count` | 8 ||
|| Maximum number of databases per cloud
`ydb.dedicatedDatabases.count` | 4 ||
|| Maximum number of storage groups per cloud
`ydb.dedicatedStorageGroups.count` | 8 ||
|#
**Serverless mode**
#|
|| Type of limit | Default value ||
|| Maximum number of databases
`ydb.serverlessDatabases.count` | 4 ||
|| Maximum number of serverless request units per second, per cloud
`ydb.serverlessRequestUnitsPerSecond.count` | 1,000 RUs ||
|| Maximum number of schema operations^*^ per day in a single serverless database
`ydb.schemaOperationsPerDay.count` | 1,000 ||
|| Maximum number of schema operations^*^ per minute in a single serverless database
`ydb.schemaOperationsPerMinute.count` | 30 ||
|| Total storage size of serverless databases
`ydb.serverlessStorage.size` | 300 GB ||
|| Number of Data Streams shards in a serverless database
`ydb.dataStreamShards.count` | 100 ||
|| Number of billable request units per second in serverless mode
`ydb.serverlessProvisionedCapacity.count` | 1,000 ||
|#
^*^Operations with quotas: creating, updating, and deleting table schemas, getting a table description, getting a list of tables, and creating and deleting directories.
## Yandex Managed Service for YTsaurus {#myt}
Service: `managed-ytsaurus`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`managed-ytsaurus.clusters.count` | 5 ||
|| Total number of processor cores for all cluster components per cloud
`managed-ytsaurus.cores.count` | 300 ||
|| Total HDD storage capacity
`managed-ytsaurus.hdd.size` | 18,432 GB ||
|| Total virtual memory for all cluster components per cloud
`managed-ytsaurus.memory.size` | 762 GB ||
|| Total non-replicated SSD storage capacity
`managed-ytsaurus.nrdssd.size` | 5,022 GB ||
|| Total SSD storage capacity
`managed-ytsaurus.ssd.size` | 5,022 GB ||
|| Total number of NVIDIA® Ampere® A100 [GPUs](../compute/concepts/gpus.md) for all cluster components per cloud
`managed-ytsaurus.a100-gpus.count` | 0 ||
|| Total number of Intel Ice Lake with T4i GPUs for all cluster components per cloud
`managed-ytsaurus.t4i-gpus.count` | 0 ||
|| Total number of NVIDIA® Tesla® V100 GPUs for all cluster components per cloud
`managed-ytsaurus.v100-gpus.count` | 0 ||
|#
#### Limits {#limits}
##### Component configuration limits {#config-limits}
**Exec nodes**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of exec nodes per cluster | 1 | 1,000 |
| Exec node class | c8-m32 (8 vCPUs, 32 GB RAM) | gpu-v3-g4 (112 vCPUs, 476 GB RAM, 4 GPUs) |
| HDD storage size | 10 GB | 102,400 GB |
| SSD storage size | 10 GB | 102,400 GB |
| Non-replicated SSD storage size | 93 GB | 102,393 GB |
**Tablet nodes**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of tablet nodes per cluster | 0 | 1,000 |
| Tablet node class | c6-m12 (6 vCPUs, 12 GB RAM) | c32-m64 (32 vCPUs, 64 GB RAM) |
**HTTP proxies**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of HTTP proxies | 1 | 10 |
**RPC proxies**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of RPC proxies | 1 | 10 |
##### Storage limits {#storage-limits}
**HDD storage**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of disks | 3 | 600 |
| Disk size | 10 GB | 102,400 GB |
**SSD storage**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of disks | 3 | 600 |
| Disk size | 10 GB | 102,400 GB |
**Non-replicated SSD storage**
| Type of limit | Minimum value | Maximum value |
|:-------------------------------|:---------------------------|:---------------------------|
| Number of disks | 3 | 600 |
| Disk size | 93 GB | 102,393 GB |
## Yandex MetaData Hub {#metadata-hub}
Service: `metadata-hub`, resource type: `resource-manager.cloud`.
### Connection Manager {#connection-manager-quota}
#|
|| Quota | Value ||
|| Total number of connections per cloud
`connection-manager.totalConnections.count` | 1,000 ||
|#
### Schema Registry {#schema-registry-quota}
#|
|| Quota | Value ||
|| Total number of namespaces per cloud
`schema-registry.namespaces.count` | 32 ||
|| Total number of schemas per cloud
`schema-registry.schemas.count` | 10,240 ||
|#
### Apache Hive™ Metastore {#metastore-quota}
Service: `managed-metastore`, resource type: `resource-manager.cloud`.
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`managed-metastore.clusters.count` | 5 ||
|#
## Yandex Monitoring {#monitoring}
Service: `monitoring`, resource type: `resource-manager.cloud`.
#### Quotas {#monitoring-quotas}
#|
|| Type of limit | Value ||
|| Number of alerts per cloud
`monitoring.alerts.count` | 30,000 ||
|| Number of metrics per service in the folder | 1,000,000 ||
|#
#### General limits {#monitoring-common-limits}
Type of limit | Value
----- | -----
Number of labels per metric
(including required ones) | 16
Number of values per label | 1,000
#### API limits {#monitoring-api-limits}
Type of limit | 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 {#monitoring-alerting-limits}
Type of limit | Value
----- | -----
Number of metrics per alert | 1,000
Number of SMS per number per day | 100
## Yandex Network Load Balancer {#load-balancer}
Service: `ylb`, resource type: `resource-manager.cloud`.
#### Quotas {#load-balancer-quotas}
#|
|| Type of limitation | Value ||
|| Number of load balancers per cloud
`ylb.networkLoadBalancers.count` | 2 ||
|| Number of target groups per cloud
`ylb.targetGroups.count` | 100 ||
|#
#### Limits {#load-balancer-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 {#load-balancer-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](../vpc/concepts/limits.md#limits) on the maximum number of concurrent TCP/UDP connections per VM.
## Yandex Object Storage {#storage}
Service: `storage`, resource type: `resource-manager.cloud`.
#### Quotas {#storage-quotas}
#|
|| Type of limit | Value ||
|| Storage volume per cloud
`storage.volume.size` | 1,024 GB ||
|| Number of buckets per cloud
`storage.buckets.count` | 25 ||
|#
#### Limits {#storage-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 number of rules for [conditional request redirects](../storage/operations/hosting/setup.md#redirects-on-conditions) for a website. | 50
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 {#yq}
Service: `query`, resource type: `resource-manager.cloud`.
#### Limits {#yq-limits}
Type of limitation | Value
--- | ---
Maximum query result retention time | 24 hours
Maximum streaming query runtime (preview) | 7 days
Maximum analytical query runtime | 24 hours
Maximum query result size | 20 MB
#### Quotas {#yq-quotas}
#|
|| Type of limitation | Value ||
|| Maximum concurrent analytical queries
`yq.analyticsQuery.count` | 100 ||
|| Maximum concurrent streaming queries
`yq.streamingQuery.count` | 100 ||
|| Maximum analytical query runtime
`yq.analyticsQueryDurationMinutes.count` | 30 minutes ||
|#
{% note warning %}
In preview, the maximum streaming query runtime is 7 days, after which the query is forcibly terminated. If you need to run streaming queries without time limits, contact Yandex Cloud support.
{% endnote %}
## Yandex Resource Manager {#resource-manager}
Service: `resource-manager`, resource type: `organization-manager.organization`.
#### Quotas {#resmgr-quotas}
#|
|| Type of limit | Value ||
|| Maximum number of clouds per organization
`resource-manager.clouds.count` | 5 ||
|| Maximum number of folders per cloud
`resource-manager.folders.count` | 50 ||
|#
#### Limits {#resmgr-limits}
There are no limits for Resource Manager.
## Yandex Serverless Containers {#serverless-containers}
Service: `serverless-containers`, resource type: `resource-manager.cloud`.
#### Quotas {#serverless-containers-quotas}
#|
|| Type of limit | Value ||
|| Number of containers per cloud
`serverless.containers.count` | 10 ||
|| Number of [triggers](../serverless-containers/concepts/trigger/index.md) per cloud^1^
`serverless.triggers.count` | 100 ||
|| Total size of Docker images used in active container revisions
`serverless.containers.size` | 20 GB ||
|| Number of container instances per availability zone
`serverless.containersInstances.count` | 10 ||
|| Number of concurrent requests to containers in each availability zone
`serverless.containersRequest.count` | 10 ||
|| Total RAM for all running container instances per availability zone
`serverless.containersMemory.size` | 20 GB ||
|| Total number of CPUs of all running container instances per availability zone
`serverless.containersCpu.count` | 10 ||
|| Number of [provisioned container instances](../serverless-containers/concepts/container.md#provisioned-instances) per cloud
`serverless.containersWorkersProvisioned.count` | 2 ||
|| Number of [user networks](../serverless-containers/concepts/networking.md#user-network) per cloud | 10 ||
|#
^1^ API Gateway, Cloud Functions, and Serverless Containers share the same `Number of triggers per cloud` quota. The [management console](https://console.yandex.cloud/cloud?section=quotas) shows it as part of the Cloud Functions quota list.
#### Limits {#serverless-containers-limits}
Type of limit | Value
----- | -----
Maximum size of a container image | 10 GB
Maximum RAM per container instance | 8 GB
Maximum [ephemeral disk](../serverless-containers/concepts/mounting.md#mount-ephemeral-storage) space per container instance | 10 GB
Maximum size of an HTTP request to a container, including HTTP headers and the request body | 3.5 MB
Maximum size of a container HTTP response, including HTTP headers and the response body | 3.5 MB
Maximum size of temporary files | 512 MB
Maximum container request processing time before timeout, including initialization at first startup^1^ | 1 hour
Maximum total size of environment variables, including their names^2^ | 4 KB
Maximum number of triggers per [message queue](../message-queue/concepts/queue.md) | 1
Maximum message size per trigger^3^ | 230 KB
^1^ A timeout of more than 10 minutes is only available for [long-lived containers](../serverless-containers/concepts/long-lived-containers.md).
^2^ Lockbox secrets are provided via environment variables and are also counted towards this limit.
^3^ A message may include service metadata, which reduces the maximum message size.
## Yandex SmartCaptcha {#captcha}
Service: `smartcaptcha`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limitation | Value ||
|| Maximum number of CAPTCHAs per cloud
`smart-captcha.captchas.count` | 10 ||
|| Maximum number of [challenge options](../smartcaptcha/concepts/captcha-variants.md) per cloud | 32 ||
|| Maximum number of [show rules](../smartcaptcha/concepts/captcha-variants.md#captcha-view-rules) per cloud | 250 ||
|#
#### Limits {#limits}
There are no limits for SmartCaptcha.
## Yandex Smart Web Security {#sws}
Service: `smartwebsecurity`, resource type: `resource-manager.cloud`.
#### Quotas {#quotas}
#|
|| Type of limit | Value ||
|| Number of [security profiles](../smartwebsecurity/concepts/profiles.md) per [cloud](../resource-manager/concepts/resources-hierarchy.md#cloud)
`smart-web-security.securityProfiles.count` | 5 ||
|| Number of [ARL profiles](../smartwebsecurity/concepts/arl.md) per cloud
`smart-web-security.advancedRateLimiterProfiles.count` | 5 ||
|| Number of [WAF profiles](../smartwebsecurity/concepts/waf.md) per cloud
`smart-web-security.wafProfiles.count` | 10 ||
|| Total number of [security profile rules](../smartwebsecurity/concepts/rules.md) per cloud
`smart-web-security.securityProfileRules.count` | 250 ||
|| Total number of [WAF exclusion rules](../smartwebsecurity/concepts/waf.md#exclusion-rules) per cloud
`smart-web-security.wafProfileExclusionRules.count` | 250 ||
|| Total number of [ARL profile rules](../smartwebsecurity/concepts/rules.md#arl-rules) per cloud
`smart-web-security.advancedRateLimiterProfileRules.count` | 250 ||
|| Total number of IP address mapping [conditions](../smartwebsecurity/concepts/conditions.md) per cloud
`smart-web-security.ipMatchers.count` | 2,500 ||
|| Number of IP address lists per cloud
`smart-web-security.ipMatchLists.count` | 20 ||
|| Number of ASN lists per cloud
`smart-web-security.asnMatchLists.count` | 20 ||
|| Number of string lists per cloud
`smart-web-security.strMatchLists.count` | 20 ||
|| Number of regular expression lists per cloud
`smart-web-security.regExpMatchLists.count` | 2 ||
|| Number of unique IP address lists per profile
`smart-web-security.uniqueIPMatchListsPerProfile.count` | 40 ||
|| Total number of IP address lists per profile (including repetitions)
`smart-web-security.ipMatchListsPerProfile.count` | 100 ||
|| Number of unique ASN lists per profile
`smart-web-security.uniqueAsnMatchListsPerProfile.count` | 40 ||
|| Total number of ASN lists per profile (including repetitions)
`smart-web-security.asnMatchListsPerProfile.count` | 100 ||
|| Number of unique string lists per profile
`smart-web-security.uniqueStrMatchListsPerProfile.count` | 40 ||
|| Total number of string lists per profile (including repetitions)
`smart-web-security.strMatchListsPerProfile.count` | 100 ||
|| Number of unique regular expression lists per profile
`smart-web-security.uniqueRegExpMatchListsPerProfile.count` | 10 ||
|| Total number of regular expression lists per profile (including repetitions)
`smart-web-security.regExpMatchListsPerProfile.count` | 10 ||
|| Number of items per IP address list
`smart-web-security.ipMatchListItems.count` | 10,000 ||
|| Number of items per ASN list
`smart-web-security.asnMatchListItems.count` | 200 ||
|| Number of items per string list
`smart-web-security.strMatchListItems.count` | 100 ||
|| Number of items per regular expression list
`smart-web-security.regExpMatchListItems.count` | 10 ||
|| Total number of [proxy servers](../smartwebsecurity/concepts/domain-protect.md#proxy) per cloud
`smart-web-security.loadBalancers.count` | 1 ||
|| Total number of [domains](../smartwebsecurity/concepts/domain-protect.md#domain) per cloud
`smart-web-security.loadBalancerDomains.count` | 10 ||
|| Total number of [response templates](../smartwebsecurity/concepts/response-templates.md) per cloud
`smart-web-security.customPages.count` | 20 ||
|#
#### Limits {#limits}
**Type of limit** | **Value**
----- | -----
Number of `HTTP header` conditions per rule | 20
Number of `Query Match` conditions per rule | 20
Number of IP addresses, prefixes, or IP address ranges per condition | 10,000
Number of `HTTP method` conditions per rule | 20
Number of `Host` conditions per rule | 20
Regular expression string length | 255 characters
Number of requests per second (RPS) in total for all load balancer [virtual hosts](../application-load-balancer/concepts/http-router.md#virtual-host)
connected to the same security profile^1^ | 20,000
Number of domains per proxy server | 20
Number of target IP addresses per domain | 20
Number of items per IP address list | 100,000
Number of items per ASN list | 2,000
Number of items per string list | 2,000
Number of items per regular expression list | 100
^1^ If you expect more requests per second, contact your Yandex Cloud account manager.
## Yandex StoreDoc {#mmg}
Service: `mdb`, resource type: `resource-manager.cloud`.
#### Quotas {#mmg-quotas}
#|
|| Type of limit | Value ||
|| Number of clusters per cloud
`mdb.clusters.count` | 16 ||
|| Total number of CPU cores for all database hosts per cloud
`mdb.cpu.count` | 64 ||
|| Total virtual memory for all database hosts per cloud
`mdb.memory.size` | 512 GB ||
|| Total storage capacity for all clusters per cloud
`mdb.ssd.size` | 4,096 GB ||
|| Number of GPUs
`mdb.gpu.count` | 0 ||
|#
#### Limits {#mmg-limits}
| Type of limit | Minimum value | Maximum value |
|:-----------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------|:-------------------------------------------------|
| Host class | b1.medium (2 × [50%](../compute/concepts/performance-levels.md) vCPU Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) |
| Number of shards per cluster | 1 | 10 |
| Number of hosts per shard when using a network HDD or SSD storage or an ultra high-speed network SSD storage with three replicas | 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](../storedoc/concepts/storage.md#storage-type-selection); the cluster [is created](../storedoc/operations/cluster-create.md) in an unsharded state. | 70 (10 shards × 7 hosts) |
| Amount of data per host when using a network HDD or SSD storage. | 10 GB | 2,048 GB |
| Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 2,232 GB |
| Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB |
| Number of databases per cluster | 1 | 1000 |
^*^ Read more on how platform selection affects [available storage types](../storedoc/concepts/storage.md).
The maximum available number of simultaneous connections to a single Yandex StoreDoc 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 Virtual Private Cloud {#vpc}
Service: `vpc`, resource type: `resource-manager.cloud`.
#### Quotas {#vpc-quotas}
#|
|| Type of limit | Value ||
|| Number of cloud networks per cloud
`vpc.networks.count` | 2 ||
|| Number of subnets per cloud
`vpc.subnets.count` | 12 ||
|| Number of all public IP addresses per cloud
`vpc.externalAddresses.count` | 8 ||
|| Number of static public IP addresses per cloud
`vpc.externalStaticAddresses.count` | 2 ||
|| Number of routing tables per cloud
`vpc.routeTables.count` | 8 ||
|| Number of static routes per cloud
`vpc.staticRoutes.count` | 256 ||
|| Maximum number of security groups
`vpc.securityGroups.count` | 10 ||
|| Maximum number of security groups per interface | 5 ||
|| Maximum number of service connections per cloud
`vpc.privateEndpoints.count` | 2 ||
|#
#### Limits {#vpc-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 groups^1^ ^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](../vpc/concepts/network.md#subnet)) | 1,000 requests per second
Maximum number of NAT gateways | 20
Maximum load per service connection^3^ | 10 Gbps
^1^ Counts all TCP and UDP connections opened and half-opened within 180 seconds. 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.
^3^ If you exceed the limits in place, the platform reserves the right to restrict the service connection. If you need to use your service connections beyond the specified limit, please contact [support](../support/overview.md).
#### Outgoing traffic filtering {#vpc-egress-traffic-filter}
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.
We recommend using [Yandex Cloud Postbox](../postbox/index.md) to send your emails. If you have any issues, contact [support](../support/overview.md).