aws / aws/containers-roadmap

[ECS] [request]: Lifecycle policies for unused task definitions to deregister

Open
#899 2 comments 21 reactions 0 assignees 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**
Lifecycle policies for automatic deregistration for unused ECS task definitions

**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 want to inactivate ECS task definitions automatically which are not referenced from ECS services for a certain period.
Immediately after deploying, sometimes we need old task-definition to rollback ECS tasks.
But after a certain period, in most cases, we don't need old task-definition anymore.
So, I want to inactivate the old task-definition after a while.

I would be happy if I could create a non-current version lifecycle setting in ECS task definition like S3.

**Are you currently working around this issue?**
with lambda function

**Additional context**
Nothing

**Attachments**
Nothing

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.