Quick answer
AWS API Gateway documents maximum integration timeout as 30 seconds. The HTTP API integration timeout is documented as non-increasable.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum integration timeoutThe HTTP API integration timeout is documented as non-increasable. | 30 seconds | HTTP APIs | Amazon Web ServicesAug 22, 2026 |
Why does this limit matter?
An upstream Lambda or service can keep running after API Gateway has already stopped waiting for the response.
This value is scoped to HTTP APIs; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm the API type and measure end-to-end integration latency at p95 and p99.
- 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
- REST APIs, WebSocket APIs, load balancers, and downstream functions have their own timeout rules.
- 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