[ECR] [request]: Auto cleanup for ECR pull through cache
- 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**
Implement an lifecycle rule feature to removed images based on their last download.
**Which service(s) is this request for?**
Fargate, ECS, EKS, ECR
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
The images aren't cleaned up automatically. Therefore a lot of storage is wasted.
**Are you currently working around this issue?**
We are deploying some custom lambda function which delete old images.
**Additional context**
Anything else we should know?
**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.)
Contributor guide
Research direction
No repository files, tests, or entry points are mentioned. Start by reviewing the ECR pull-through cache behavior and the custom Lambda workaround described in the issue. Done means an ECR lifecycle rule can remove images based on their last download, covering the listed container services.
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
- Mostly clear
- Newbie friendliness
- 30/100