Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

What the maximum default timeout for API Gateway can be increased to after applying for a Service Quotas limit increase.

0

I have created several private REST APIs in the Tokyo region, and the backend is configured to invoke a Lambda function that runs batch jobs. In this scenario, I would like to understand what the maximum possible execution timeout for API Gateway is after adjustment.

The request frequency of these APIs is very low, but I want to ensure that increasing the timeout will not negatively impact the performance of other APIs in the same region. Those other APIs should continue to use the default timeout of 29 seconds.

  • mo6
    2 months ago

    ■ API Gateway Integration Timeout Limit By submitting a request via Service Quotas, you can extend the API Gateway integration timeout from the default of 29 seconds (29,000 ms) up to a maximum of 300 seconds (300,000 ms / 5 minutes). However, this increase applies only to Regional REST APIs and Private REST APIs. Please note that Edge-optimized REST APIs and HTTP APIs (v2) are not eligible for this limit increase.

    ■ Notes When extending the timeout, you may be required to reduce the account- and region-level throttling limit (default: 10,000 RPS). For example, if the timeout is set to 300,000 ms (5 minutes), the RPS limit may be reduced to approximately 967. Please also consider the impact on other workloads. In addition, after the request is approved, you will need to manually update the timeout setting in the API Gateway console and redeploy the API.

Topics
ServerlessFront-End Web & MobileComputeNetworking & Content Delivery
Tags
Amazon API GatewayService QuotasAWS Lambda
Language
English
asked 2 months ago174 views
1 Answer
1
Accepted Answer

For private REST APIs in API Gateway, you can increase the integration timeout beyond the default 29 seconds by requesting a quota increase through the Service Quotas console. When submitting your request, you would select the "Maximum integration timeout in milliseconds" quota and enter a value greater than 29,000 milliseconds.

However, there's an important consideration: while you can raise the integration timeout to greater than 29 seconds, doing so might require a reduction in your Region-level throttle quota for your account. The integration timeout also cannot be set to less than 50 milliseconds.

Regarding your concern about other APIs in the same region, the good news is that you can configure timeout settings at the individual API integration level. After your account-level quota increase is approved, you can selectively update only the specific APIs that need the extended timeout by editing their integration request settings in the API Gateway console. This means your other APIs can continue using the default 29-second timeout without being affected.

For your batch job scenario with low request frequency, this approach should work well - you can set a longer timeout for your Lambda-backed batch APIs while maintaining the standard timeout for your other APIs in the Tokyo region. Just be aware of the potential impact on your account's throttle quota when requesting a significantly higher integration timeout value.
Sources
Increase the API Gateway integration timeout limit | AWS re:Post
Quotas for configuring and running a REST API in API Gateway - Amazon API Gateway

answered 2 months ago
EXPERT
reviewed 2 months ago
EXPERT
reviewed 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content