Quick answer
AWS API Gateway documents http api resources as 300 routes and 300 integrations per API. Route quota can be increased; integration count is documented as non-increasable.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| HTTP API resourcesRoute quota can be increased; integration count is documented as non-increasable. | 300 routes and 300 integrations per API | HTTP APIs | Amazon Web ServicesAug 22, 2026 |
Why does this limit matter?
Generated route-per-tenant designs can exhaust control-plane resources before traffic quotas matter.
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?
- Inventory routes and unique integrations in the deployed API before adding generated resources.
- 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
- Stages, authorizers, mappings, and tags have independent counts.
- 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