Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| function memory rangeCPU capacity scales with configured memory. | 128 MB to 10,240 MB | Per function | Amazon Web ServicesAug 22, 2026 |
| Function timeoutA function-level configuration ceiling; the configured timeout may be lower. | 900 seconds (15 minutes) | Platform documented | Amazon Web ServicesAug 22, 2026 |
| Synchronous request and responseAWS uses MB in Lambda docs to mean 1,024 KB. | 6 MB each | Synchronous invocation | Amazon Web ServicesAug 22, 2026 |
| Streamed synchronous responseBandwidth is uncapped for the first 6 MB and limited for the remainder according to AWS documentation. | 200 MB | Streamed synchronous response | Amazon Web ServicesAug 22, 2026 |
| Asynchronous invocation payloadSmaller than the synchronous request/response constraint. | 1 MB | Asynchronous invocation | Amazon Web ServicesAug 22, 2026 |
How to apply AWS Lambda limits safely
The monitored baseline covers function memory range, Function timeout, Synchronous request and response, Streamed synchronous response, Asynchronous invocation payload. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.
- Match the production workload to the exact scope printed beside each value and confirm it in the active AWS Lambda console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.
Specific limit pages
These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.
AWS Lambda Memory Limit
AWS Lambda Memory Limit, verified against AWS Lambda's official documentation with scope, implementation impact, caveats, and a direct check.
AWS Lambda timeout
The current AWS Lambda maximum function timeout, how configured timeouts differ from the ceiling, and what to inspect before increasing it.
AWS Lambda payload limits
Current Lambda request and response payload limits for synchronous, asynchronous, and streamed invocation paths.
Errors linked to these limits
Task timed out after … seconds
AWS Lambda Task Timed Out Error: direct meaning, scoped diagnosis, corrective action, official source, and linked current limit.
413 — Payload Too Large
AWS API Gateway 413 Payload Too Large: direct meaning, scoped diagnosis, corrective action, official source, and linked current limit.
Compare alternatives
Cloudflare Workers vs AWS Lambda Limits
Cloudflare Workers vs AWS Lambda Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Google Cloud Run vs AWS Lambda Limits
Google Cloud Run vs AWS Lambda Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Azure Functions vs AWS Lambda Limits
Azure Functions vs AWS Lambda Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Netlify vs AWS Lambda Function Limits
Netlify vs AWS Lambda Function Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Vercel vs AWS Lambda
Compare current execution duration and payload constraints across Vercel Functions and AWS Lambda by invocation mode.