Configurable request timeout

**Community Note** * Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request If you are interested in working on this issue or have submitted a pull request, please leave a comment **Tell us about your request** Currently AppRunner enforces a 30 second timeout on HTTP requests. If the timeout is hit, a HTTP 503 response is returned. For some use cases, especially large file uploads, this is a severe limitation. **Describe alternatives you've considered** We first refactored our file upload to use S3 multi-part uploads to break the upload request into several shorter requests. But then we ran into the problem that the S3 complete_multipart_upload call can take a long time (several minutes) to complete. We are now considering having the user upload directly to S3, and then notifying the AppRunner service of the completed upload. If that avenue is unsuccessful, we will move to EC2, but that would be a shame as AppRunner has worked well for us so far. **Additional context** AWS support case ID (9433361761) **Attachments** Behavior can be easily triggered by calling something that takes longer than 30 seconds (in this case, a dummy "sleep" route) ``` > GET /sleep?seconds=31 HTTP/1.1 > Host: xxxx.eu-west-1.awsapprunner.com > User-Agent: curl/7.64.1 > Accept: */*

Posted by suzukieng on Jan 18, 2022, 9:10 AM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [RFC] Roadmap to v2.0