Platform hub

AWS API Gateway limits

HTTP API integration timeout, payload, route, header, and resource quotas. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  AWS API Gateway has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
maximum integration timeoutThe HTTP API integration timeout is documented as non-increasable.30 secondsHTTP APIsAmazon Web ServicesAug 22, 2026
request payloadThe payload quota is documented as non-increasable.10 MBHTTP APIsAmazon Web ServicesAug 22, 2026
HTTP API resourcesRoute quota can be increased; integration count is documented as non-increasable.300 routes and 300 integrations per APIHTTP APIsAmazon Web ServicesAug 22, 2026

How to apply AWS API Gateway limits safely

The monitored baseline covers maximum integration timeout, request payload, HTTP API resources. 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.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active AWS API Gateway console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. 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.

Compare alternatives

Official sources

View AWS API Gateway change history