AWS Rate Limit Troubleshooting
If you get an error message:
while calling a Lambda function, it means your concurrency limit has been reached.
- Concurrency limit: The maximum amount of Lambda functions that can run concurrently per region per account.
- Burst limit: The maximum amount of concurrency increase in 10 seconds (the burst limit is 1000)
Default concurrency limits
By default, the concurrency limit is 1000 functions per region, however in some regions the burst limit is only 500, somewhat limiting the scale you can use.
New accounts using AWS Lambda
According to AWS, "some accounts" which are new to AWS Lambda might get a very low concurrency limit such as 10 when they first start with AWS Lambda. In that case, increase the limit via the AWS console or the Remotion CLI (see below).
Workaround
If you want to test Remotion Lambda while you are waiting for AWS to approve a higher concurrency limit, you can pass a higher number to framesPerLambda.
For example: If your account currently has a concurrency limit of 10 and you want to render a composition with 900 frames, you can set framesPerLambda to 100.
9 Lambda renderer functions will be spawned: 900 / 100 = 9.
An additional Lambda function will be spawned for orchestration, meaning a total of 10 Lambda functions will be used, keeping yourself within your limit.
See your limits
To see your limits, run
If you get a permission error, repeat the user policy step in the Setup Guide and update your user policy file in the AWS console.
Request an increase
You can request a quota increase under https://console.aws.amazon.com/servicequotas/home or using the Remotion CLI:
This only works for AWS Root accounts, not the children of an organization. You can still request an increase via the console.
See here for a default answer if AWS asks why you requested the increase.
Unhelpful?
Contact the Remotion team, preferrably via Discord and we will be happy to help you with your rate limit problem.