aws / aws/containers-roadmap

[ECS] [Managed Instances Target Capacity]: Allow configuration of reserve capacity

Open
#2,724 0 comments 0 reactions 1 assignee Claimed by @AbhishekNautiyal View on GitHub
ECS Proposed
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**
When using managed instances for ECS, i would like to be able to configure a target capacity like we can do with auto scaling groups. Currently managed instances really nicely optimizes the placement of tasks, but this means in practice that new tasks sometimes have to wait for a new instance to come online. By allowing configuration of this target capacity (e.g. 90%) I can be sure that new tasks are placed immediately while new instances spin up.

**Which service(s) is this request for?**
ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Usual start time of new tasks is still often faster or as fast as fargate, but we'd like to be able to scale a bit faster when we need to.

**Are you currently working around this issue?**
Fargate, self managed

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.