[Yandex Cloud documentation](../../index.md) > [Yandex Serverless Containers](../index.md) > [Concepts](index.md) > Quotas and limits

editable: false
---

# Quotas and limits Serverless Containers

Serverless Containers has the following limits:

* [_Quotas_](https://console.yandex.cloud/cloud?section=quotas) are organizational constraints that can be changed by contacting technical support.
* _Limits_ are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

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

* [Make a request to increase your quotas](https://console.yandex.cloud/cloud?section=quotas).
* Contact [support](https://center.yandex.cloud/support) and specify which quotas you want increased and by how much.

To have your request processed, you must have the `quota-manager.requestOperator` [role](../../iam/roles-reference.md#quota-manager-requestoperator) or higher, e.g., `editor` or `admin`.

You can manage your quotas with [Cloud Quota Manager](../../quota-manager/quickstart.md).

#### Quotas {#serverless-containers-quotas}

#|
|| Type of limit | Value ||
|| Number of containers per cloud 
`serverless.containers.count` | 10 ||
|| Number of [triggers](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](container.md#provisioned-instances) per cloud 
`serverless.containersWorkersProvisioned.count` | 2 ||
|| Number of [user networks](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](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](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.