Quick answer
AWS Lambda documents function memory range as 128 MB to 10,240 MB. CPU capacity scales with configured memory.
Verified Aug 22, 2026Official source
Current 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 |
Why does this limit matter?
Increasing memory can shorten CPU-bound work as well as increase the memory ceiling.
This value is scoped to Per function; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Read deployed memory and compare duration/cost profiles across representative settings.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Regional concurrency and account quotas still govern aggregate execution.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related