Autoscale based on CPU and/or memory
- 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**
Ability to specify autoscaling based on cpu % or memory instead of number of requests
Contributor guide
Research direction
This roadmap issue names no files, tests, or entry points. Start by reviewing the existing App Runner autoscaling behavior and documentation for request-based scaling, then determine where CPU and memory targets would be specified and verified. Done means CPU and/or memory percentage-based autoscaling is supported alongside the current request-count model.
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