Best practices for long-running API Gateway requests


API Gateway has a max connection of 29 seconds. A customer would like to use API Gateway for longer-running requests. What can we provide in terms of best practices to achieve this? My initial thoughts are around making the request "job based" (short lived POST, then GET polls to get job status) but that requires rearchitecting their application and adding job state.

Do we have blog posts or whitepapers to recommend best practices around this?

profile picture
asked a year ago439 views
1 Answer
Accepted Answer

29 sec is the max timeout as of now which works for a majority of use cases. It would be better if you explain what kind of request is it that lasts more than 29 secs. Keep in mind that there might be proxies in the path whose timeout you may not be able to control.

ALB does not have such a limit. It might be a better solution in this case, without knowing anything else. But you won't benefit from rate limiting, throttling, API Keys, etc.

Separating request into POST and then GET polling is an alternative. WebSockets might be another one.

That said, this timeout may or may not be under revision. Even if it is, 29 sec is the limit right now.

answered a year 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.

Guidelines for Answering Questions