Request Timout parity with other platforms and tools
- Dominant language
- No language data
- Stars
- 301
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
**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**
Please increase the maximum timeout of an HTTP request to AppRunner to be more inline with other platforms:
Lambda - 600 seconds
Elastic Beanstalk - Unlimited
Google Cloud Run - 60 minutes
Azure Container Instances: unlimited
There are many use cases for long lived http requests which do *not* fit will with an async pattern or with something like AWS batch.
**Describe alternatives you've considered**
These other platforms mentioned above.
**Additional context**
If you are trying to protect a resource like load balancer connections... then simply add it to the cost model and let us decide.
Contributor guide
Research direction
This is an AWS App Runner roadmap request to increase the maximum HTTP request timeout; no repository files, tests, or implementation entry points are named. Start by confirming the current limit and the service constraints, then discuss the requested parity with maintainers; done would require an accepted product change rather than a repository patch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100