Quotas and limits
In the Cloud Functions service, the following limitations apply:
- Quotas are organizational restrictions that can be changed by technical support on request.
- Limits are technical restrictions due to the Yandex.Cloud architecture specifics. The limits cannot be changed.
Quotas
| Type of limit | Value |
|---|---|
| Number of functions per cloud | 10 |
| Number of instances of a single function in each availability area | 10 |
| Number of concurrent function calls (for all functions in each availability zone) | 10 |
| Total RAM for all running functions in each availability zone | 20 GB |
Function instance processes one function call at a time. If there are more function calls than instances available, the call is queued. A queued call is treated as a call-in-progress and consumes your quota.
Calls are distributed across availability zones randomly. Cloud Functions does not guarantee even distribution of calls across zones. For example, all calls, regardless of their number, might occur in the same zone.
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 request's JSON structure | 3.5 MB |
| Maximum temporary file size | 512 MB |
| Maximum function execution time before timeout (including original initialization at first call) | 10 minutes |
| Maximum number of triggers per message queue | 1 |
Other restrictions
- The trigger must be in the same cloud as the queue that messages are read from.
- When installing dependencies:
- The total time to install dependencies is limited to 5 minutes. After it expires, the build fails with an error.
- The command for installing dependencies is allocated no more than 1 GB of RAM.