[ECS/Fargate] [Feature request]: Service AutoScaling TargetTracking Policy Scaling Aggressiveness
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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**
What do you want us to build?
Service AutoScaling TargetTracking Policies will increase/decrease the number tasks based on the threshold configured, however there is no method to configure the aggressiveness as this is all internal logic. Maybe something can be implemented to choose the aggressiveness from auto, relaxed, very aggressive, which let's TargetTracking policies to determine how much task it can add/removed at a time.
**Which service(s) is this request for?**
Fargate, ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
With a strict scaling logic requirement, it is a pity that TargetTracking policies lacks configurability on how aggressive scaling can happen, as it is easier to configure when compared to StepScaling policies.
**Are you currently working around this issue?**
How are you currently solving this problem?
StepScaling policies.
**Additional context**
Anything else we should know?
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Contributor guide
Assessment
This issue has not been assessed yet.