Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean AWS Lambda has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 5 scoped observations for AWS Lambda. The baseline covers function memory range, Function timeout, Synchronous request and response, Streamed synchronous response, Asynchronous invocation payload. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| 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 |
Tracked constraints and impact
Execution, memory, payload, deployment, storage, and regional quotas. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
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.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current AWS Lambda baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Function configuration, deployment, and execution