[ECS] [request]: Draining ECS container instance should drain target group before task is stopped
- 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 a ECS container instance is drained, the target group associated (if the task is in a service) should be drained before the task is stopped, in order to prevent service outages.
**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?**
I cannot solve this by my own because the task always stops before I can do anything.
Contributor guide
Research direction
The request concerns ECS container-instance draining and associated target groups, but the payload names no repository files, tests, or implementation entry points. Start by identifying where ECS draining behavior is defined; done would require ensuring the target group drains before the task stops without causing service outages.
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
- Needs clarification
- Newbie friendliness
- 20/100