I have an apigateway -> lambda setup. I have raised a quota increase for api gateway integration timeout and the new limit is set to 59000ms. The lambda has a timeout of 10 mins and keeps running in background even after api gw fails with 502.

Even then I see api gw throwing 502 gateway timeout errors when requests reach (~30 secs). Is there additional I need to do to increase this limit ?

I have an apigateway -> lambda setup. I have raised a quota increase for api gateway integration timeout and the new limit is set to 59000ms. The lambda has a timeout of 10 mins and keeps running in background even after api gw fails with 502.

Even then I see api gw throwing 502 gateway timeout errors when requests reach (~30 secs). Is there additional I need to do to increase this limit ?

• amazon-web-services
• aws-api-gateway

Share Improve this question Follow edited Mar 10 at 15:19 Naxi asked Mar 10 at 14:50 NaxiNaxi 2,12477 gold badges4747 silver badges100100 bronze badges 4

• 1 Whenever dealing with api gateways and changes seemingly not having an effect: did you ensure the new changes are "deployed" to the right stage? – luk2302 Commented Mar 10 at 14:58
• 1 yes. That was the first thing i made sure I did. – Naxi Commented Mar 10 at 15:02
• Is there a load balancer involved. If so, you could be getting a response form the alb. – Ross Bush Commented Mar 10 at 15:07
• no ALB. Just the API Gw and lambda. – Naxi Commented Mar 10 at 15:08

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

Apparently, increasing timeout on Api gateway is just applicable to regional and private APIs. Mine was EDGE hence even though on api level timeout was 59 secs , it was still timing out after 30 secs.

Also, if you have a custom domain name mapped to this api, make sure that is also regional/private. Mine was "edge".

So now, i can call api using its default url and i see it waits for more than 30 secs whereas if i use custom domain name (which is edge), it again fails at 30 secs.

hope it helps someone !