Written by
Updated at December 16, 2024
editable: false
Quotas and limits Serverless Containers
Serverless Containers has the following limits:
- Quotas
are organizational restrictions that can be changed by technical support. - Limits are technical limitations due to Yandex Cloud architectural features. You cannot change the limits.
If you need more resources, you can increase quotas in one of the following ways:
- Generate a request for a quota increase
. You must have thequota-manager.requestOperator
role or higher, such aseditor
oradmin
. - Contact technical support
and tell us which quotas you want increased and by how much.
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 |
Number of user networks per cloud | 1 |
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 |
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.