[ECS] [request]: Stop and Start a Container with same Container ID
- 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?
-> A feature where ECS container could be stopped and then re-started with the same container ID.
**Which service(s) is this request for?**
This could be Fargate, ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently, when we stop a running container, a new container will be launched in with a different Container ID.
Contributor guide
Research direction
This is a roadmap request for Fargate/ECS to stop and restart a container with the same container ID. No repository files, tests, or implementation entry points are named, so start by clarifying the service constraints and acceptance criteria with maintainers; done means a stopped container can be restarted with its original ID.
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
- 25/100