Skip to main content

Lambda Limits

The standard AWS Lambda quotas apply (see here), most notably:

  • Concurrency: By default, the maximum concurrent executions per region per account is 1000 executions. This limit might be lower for new accounts and users within an enterprise.
  • Burst concurrency: AWS may limit your ability to spawn a lot Lambda functions in a short amount of time. By default, this is 3000 functions at a time.
  • Storage: Configurable, limited to 10GB at most
  • RAM: Configurable, limited to 10GB at most
  • Execution limit: Configurable, at most 15 minutes

Upgrading your concurrency limit​

For scaling your renders, you should request a quota increase under https://console.aws.amazon.com/servicequotas/home or using the Remotion CLI:

npx remotion lambda quotas increase
npx remotion lambda quotas increase

This only works for AWS Root accounts, not the children of an organization. You can still request an increase via the console.

If AWS asks you for the reason​

AWS might ask you why you want to increase your concurrency limit. Commonly they send you this questionnaire.

If you would still like a higher limit, please provide the following:

  1. The main lambda functions ARNs of this application
  2. Expected transactions per second per function
  3. Expected duration per function
  4. How is each function invoked
  5. What services or resources do primary functions interact with
  6. Time periods of high demand that demonstrate approaching the provided concurrency limit.

You can answer it as follows:

  1. The functions are [function-names]

You can get a list of Remotion Lambda functions using npx remotion lambda functions ls -q.

  1. The transactions per second are very low. [Provide a rough estimation]
  2. The duration is usually around 30 seconds to 1 minute.
  3. In development phase it will be invoked via the Remotion CLI, and in production via a NodeJS app.
  4. FFmpeg and Puppeteer. The npm package is called @remotion/lambda.
  5. The process has a rendering strategy of splitting the rendering in multiple threads, to speed up the result. That is the reason why the quota increase is needed, as explained here: https://www.remotion.dev/lambda

This response has previously been successfully used to obtain an increase of the concurrency limit.

See also​