Functions limitations
This section contains usage limits that apply when using Serverless Functions.
| Resources | Criteria | Limits | Scope |
|---|---|---|---|
| Namespaces | Max number | 100* | Project |
| Functions | Max number | 1000* | Organization |
| Total function memory** | Max size | 600 GiB | Organization |
| Custom domains | Max number | 50 | Function |
| Zip size | Max size | 100 MiB | Function |
| Code size | Max size | 500 MiB | Function |
| Temporary disk size | Max size | 1024 MiB | Function instance |
| Invocation rate | Max number | 5000 per second | Function |
| Concurrency (number of simultaneous requests)*** | Max | 1 | Function instance |
| Scaling (number of simultaneous function instances) | Max | 50 | Function |
| Environment variables | Max number | 100 | Function + Namespace |
| Environment variables | Max size | 1000 chars | Environment variable |
| Secret environment variables | Max number | 100 | Function + Namespace |
| Secret environment variables | Max size | 65536 bytes | Secret environment variable |
| Time before scale to zero | Time | 15 minutes | Instance |
| Time before scale down | Time | 30 seconds | Instance |
| HTTP request duration**** | Max | 60 minutes | Request |
| Private Networks attached | Max | 1 | Function |
| Payload | Max size | 6 MiB | Request |
| Logs | Logs | 30000 per minute | Project |
* Lower limits may apply before account verification. Contact our support team if you have any questions.
** Total function memory is the sum of the memory allocated to all your functions at their maximum Scale.
*** Each instance of a function can handle a single request at a time, but a function can have several instances running at the same time.
**** Maximum duration of a single HTTP request before this request is timed out. Use Serverless Jobs for tasks up to 24h.
These limits are enforced as Organization quotas.
If the limits are exceeded during the execution of the function, a restart occurs.
Configuration restrictions
To ensure the proper functioning of the product, we restrict the use of certain ports and environment variables.
Blocked ports
Due to potential abuse (spam), no outbound traffic is allowed through following ports, except from Scaleway Transactional Email SMTP servers.
- 25
- 465
Reserved environment variables:
SCW_*: Reserved for product configuration (for example: token validation).
Dedicated IP
Not available: Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product.
Private Networks and Virtual Private Cloud (VPC)
Compatibility
Scaleway Serverless Functions support Virtual Private Cloud (VPC) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the dedicated documentation for more information.
Limitations
-
VPC is only compatible with functions using sandbox V1 for the moment.
-
VPC works with Namespaces that have VPC support enabled. VPC support can only be enabled at namespace creation, and cannot be updated afterward.
-
Only one Private Network can be attached to a function.
Versioning and rollback
Scaleway Functions do not currently support versioning or automatic rollback mechanisms. However, in the event of a failed deployment, the previously deployed version of the function will continue to handle incoming requests for up to 24 hours. After this period, the function in error will be deleted, and requests will no longer be served until a successful deployment is made. This ensures temporary service continuity, but it is important to monitor and resolve deployment issues promptly, as the fallback is not intended to provide long-term version control or rollback capabilities.
Below is an example than illustrates this behavior:
- Time +0H: The first function is deployed and works correctly.
- Time +1H: The function is redeployed, but the deployment fails, and the function ends up in an error state.
- Time +2H: Despite the failed deployment, the first function is still handling incoming requests.
- Time +25H: The 24-hour window expires, and both the first working function and the failed function are removed, leading to service disruption until a new successful deployment is made.