Skip to content
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.

Alarming on ECR registry size #68

Open
emilymdubois opened this issue Aug 26, 2016 · 3 comments
Open

Alarming on ECR registry size #68

emilymdubois opened this issue Aug 26, 2016 · 3 comments

Comments

@emilymdubois
Copy link
Contributor

Moving this comment on PR #63 into its own issue:

When I investigated a few days ago, there din't seem to be a way to alarm on ECR. Curious if we have creative ways to use CustomMetrics at our disposal to setup ECR registry size.

cc @rclark @yhahn @emilymcafee

@rclark
Copy link
Contributor

rclark commented Aug 26, 2016

I think this would involve a scheduled lambda function that just counts images in the ECR repos. It could either put a custom metric and a correlated alarm fires when the metric is above a threshold, or the lambda function could directly trip an alarm when it detects too many images.

@emilymdubois
Copy link
Contributor Author

emilymdubois commented Aug 26, 2016

I'm sprinting next week on internal tools, but happy to jump on this afterwards if no one's grabbed it.

@emilymdubois
Copy link
Contributor Author

Changing course on this. Instead of alarming on registry size, I'm experimenting with adding automatic cleanup when an image is created and uploaded to the registry 👉 #97

@emilymdubois emilymdubois removed their assignment Aug 31, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants