# API Gateway Integration Timeout extended

**URL:** <https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268>\
**Category:** Serverless Framework\
**Tags:** aws, lambda, api-gateway\
**Created:** [June 13, 2024, 1:01pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268 "2024-06-13T13:01:33Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![willk](https://avatars.discourse-cdn.com/v4/letter/w/ee59a6/32.png) [@willk](https://forum.serverless.com/u/willk)\
**Post date:** [June 13, 2024, 1:01pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/1 "2024-06-13T13:01:33Z")

</div>

With AWS now enabling the ability to increase timeouts.

> **[Amazon API Gateway integration timeout limit increase beyond 29 seconds - AWS](https://aws.amazon.com/about-aws/whats-new/2024/06/amazon-api-gateway-integration-timeout-limit-29-seconds/)**
>
> Discover more about what's new at AWS with Amazon API Gateway integration timeout limit increase beyond 29 seconds

How would one go about setting the timeout for an integration in serverless?

Currently the gateway is setup through the provider section and a lambda attached with an http event.

Setting the timeout through the provider or the lambda function does not seem to update the integration timeout.

---

<div class="post-metadata">

**Author:** ![miljo-simelabs](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/miljo-simelabs/32/8085_2.png) [@miljo-simelabs](https://forum.serverless.com/u/miljo-simelabs)\
**Post date:** [October 4, 2024, 6:21am UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/2 "2024-10-04T06:21:30Z")

</div>

@willk any updates for this ?

---

<div class="post-metadata">

**Author:** ![ashishjullia19](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/ashishjullia19/32/8154_2.png) [@ashishjullia19](https://forum.serverless.com/u/ashishjullia19)\
**Post date:** [November 11, 2024, 11:56pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/3 "2024-11-11T23:56:28Z")

</div>

@miljo-simelabs @willk any updates on this yet?

---

<div class="post-metadata">

**Author:** ![TomC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/tomc/32/4002_2.png) [@TomC](https://forum.serverless.com/u/TomC)\
**Post date:** [November 15, 2024, 8:42am UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/4 "2024-11-15T08:42:36Z")

</div>

I know adding `timeout` to the event handlers lets you raise from the default (6s) to the default max (29s) because we’re had to do it 🙂

We’ve not raised our account quota beyond this, so I can’t easily see if setting it higher works.

Have you got AWS to raise the account limit before trying to deploy ?

---

<div class="post-metadata">

**Author:** ![willk](https://avatars.discourse-cdn.com/v4/letter/w/ee59a6/32.png) [@willk](https://forum.serverless.com/u/willk)\
**Post date:** [November 15, 2024, 1:29pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/5 "2024-11-15T13:29:58Z")

</div>

Unfortunately I did not find a setting to change it, so I ended up building a script in my pipeline to manually set the timeout via aws cli.

---

<div class="post-metadata">

**Author:** ![willk](https://avatars.discourse-cdn.com/v4/letter/w/ee59a6/32.png) [@willk](https://forum.serverless.com/u/willk)\
**Post date:** [November 15, 2024, 1:33pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/6 "2024-11-15T13:33:00Z")

</div>

Unfortunately this did not work for me, so I had to ask aws to increase the timeout in the account. After increasing I still needed to set the timeouts via a script since the current serverless config did not allow me to set it beyond the default max.

---

<div class="post-metadata">

**Author:** ![TomC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/tomc/32/4002_2.png) [@TomC](https://forum.serverless.com/u/TomC)\
**Post date:** [November 15, 2024, 3:16pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/7 "2024-11-15T15:16:21Z")

</div>

That’s exactly what you need to do, yes. It’s outlined at the top of the [Amazon API Gateway quotas and important notes - Amazon API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#api-gateway-execution-service-limits-table) page

---

<div class="post-metadata">

**Author:** ![raul\_h](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/raul_h/32/8415_2.png) [@raul\_h](https://forum.serverless.com/u/raul_h)\
**Post date:** [August 7, 2025, 1:32pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/8 "2025-08-07T13:32:01Z")

</div>

We created a plugin to solve it in serverless 3. Is there any new setting to support it natively in serverless 4?

---

<div class="post-metadata">

**Author:** ![colhugs230](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/colhugs230/32/8447_2.png) [@colhugs230](https://forum.serverless.com/u/colhugs230)\
**Post date:** [September 30, 2025, 5:05pm UTC](https://forum.serverless.com/t/api-gateway-integration-timeout-extended/20268/9 "2025-09-30T17:05:56Z")

</div>

Yes, it is natively supported in v4. Info here: [Serverless Framework - AWS Lambda Events - REST API (API Gateway v1)](https://www.serverless.com/framework/docs/providers/aws/events/apigateway#timeout)
