aws / aws/containers-roadmap

[ECR] [request]: Add CloudWatch metrics for number of tags per repository per region

Open
#2,558 0 comments 0 reactions 0 assignees View on GitHub
ECR 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**
Request to add CloudWatch metrics that show the number of tags for a given ECR repository in a specific region.

**Which service(s) is this request for?**
Amazon Elastic Container Registry (ECR)

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently, there's no straightforward way to monitor the growth of image tags within ECR repositories. This metric is crucial for:
- Monitoring repository growth and managing costs
- Setting up automated alerts when repositories exceed certain tag thresholds
- Capacity planning and cleanup scheduling

**Additional context**
This feature would complement the existing FR #578 for repository count and image count metrics providing a complete view of ECR resource usage. The metric would be particularly valuable for organizations managing multiple repositories with automated CI/CD pipelines that generate numerous tags.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the request for CloudWatch metrics on ECR repository tags and the related FR #578 for repository and image count metrics. Define the metric scope for a repository in a specific region, including how it supports growth monitoring, alerting, capacity planning, and cleanup scheduling; done means the requested feature is specified and available.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.