Closed jvisker closed 1 year ago
I have an answer from AWS support that it is currently hard-capped at 30 seconds, and it's a known limitation of AppRunner. AWS support asked me to open an issue here, which I will do shortly (separately from this one)
See #104
Can I piggy back on this to also request that this be documented:
Thank you for these suggestions. Taking a look.
Is there any strong reason for 30s timeouts?
That makes App Runner badly suited for workloads that deal with long running jobs, like analytics.
Yes, this is a known limitation at the moment and is a roadmap issue. The service team is working on it. Sorry, if this limitation is causing inconvenience for you.
@keerataws
Thank you for the quick response. Since this issue has "Documentation" in the title, I thought only documentation was being addressed, which is why I asked about the timeout itself. Very happy to know that timeouts might be increased one day!
Thank you for your feedback. We have updated the request read timeout in App Runner from 30 seconds to 120 seconds. Our documentation has also been updated.
Documentation link: https://docs.aws.amazon.com/apprunner/latest/dg/develop.html#develop.considerations
Thanks @snnles!
Good stuff, thank you @snnles !
Community Note
Tell us about your request Document how long requests can last. Empirically it looks like they are always cut off at 2 minutes, but this repost question and comment seem to indicate 30 seconds (https://repost.aws/questions/QUK3YcHzS6SVCvbF-UkWptOw/app-runner-request-timeout-http-503).