Update ECR lifecycle policy to cut costs #36
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This retains only 100 images with master/main prefixed tags, 100 of any other tag, and any other images less than 90 days old.
I haven't fully thought through the implications of changing this on every ECR repo we have, but putting up a PR anyway to start a discussion.
For reference, we're spending roughly $670/mo on ECR storage in the remind AWS accounts.
To roll this out, we'll have to cut a new
v1.x.y
release and then trigger all the CircleCI pipelines that use the orb, and they should all update the lifecycle policy for their ECR repos.