[ECS] [Request]: Feature to stop a ECS service without deleting it
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
**Tell us about your request**
What do you want us to build?
One of feature that I find missing is lack of stopping a ECS service (on demand or scheduled).
**Which service(s) is this request for?**
This could be ECS backed by EC2
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
As of today if I want some of my services to stop at night (as no one will be using it) and others to continue to run, I can't do it as it (ECS Service) maintains a minimum desired count (greater than 0).
**Are you currently working around this issue?**
How are you currently solving this problem?
Right now I am deleting the undesired services when I don't want to intend to. This is some what acceptable while working in non production environments, but in production I make the desired count to 1, as people does not look comfortable deleting and recreation approach in production.
**Additional context**
Anything else we should know?
We are using PaaS (open source cloud foundary) internally, which provides such features.
This is making me difficult to justify the cost of one ever running container in production.
**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.)
Regards,
Lalit Kumar
lalitkumarbansalaws@gmail.com
Contributor guide
Research direction
The request concerns ECS services backed by EC2 and describes deleting services as the current workaround. Start by reviewing ECS service desired-count behavior and how on-demand or scheduled stopping could differ from deletion; done would mean stopping selected services while preserving them for later restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100