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
App Runner's documentation should be more transparent and warn users about the potential traffic drops due to error 429 Too Many Requests when App Runner is scaling out so that users can adjust the max concurrency value and other configurations accordingly.
Describe alternatives you've considered
I suppose App Runner can always be better and faster at scaling out, and the max concurrency value can be higher.
Additional context
Please see attachments. We eventually mitigated this by setting the max concurrency value to the maximum (200) and a longer request timeout for the requesting server.
Community Note
Tell us about your request
App Runner's documentation should be more transparent and warn users about the potential traffic drops due to error 429 Too Many Requests when App Runner is scaling out so that users can adjust the max concurrency value and other configurations accordingly.
Describe alternatives you've considered
I suppose App Runner can always be better and faster at scaling out, and the max concurrency value can be higher.
Additional context
Please see attachments. We eventually mitigated this by setting the max concurrency value to the maximum (200) and a longer request timeout for the requesting server.
Attachments
Metrics from our App Runner:
Information shared by your colleague:
