Skip to main content
orphan · aws

Idle CodeCommit repositories: a rule retired because no per-repo saving exists

resource types
1
rule IDs covered
1
severity
low

What does ZopNight detect here?

CodeCommit prices per active user at the account level, $1 per user monthly after the first 5, so deleting one idle repository reclaims nothing: the developer stays active elsewhere and the fee persists. ZopNight retired this rule in place; today the check abstains on every repository, permanently and by design.

Signal and threshold

How ZopNight evaluates Idle CodeCommit repositories: a rule retired because no per-repo saving exists.
Field Value
Rule IDsRC-185
Categoryorphan
Severitylow
Metricnone — pure configuration read
Sourcecodecommit_idle.go

A rule that always abstains, and why that is the honest state

This entry exists in the catalogue but produces no findings, ever. The evaluation returns nothing unconditionally, and the reason is worth understanding because it generalises: CodeCommit has no per-repository price. Billing is per active user at the account grain: the first 5 users free, then a flat $1 per additional active user per month, with each active user carrying a generous free allowance (10 GB-month of storage and 2,000 Git requests). A repository is not a billable object at all.

The fabrication this retirement removed

An earlier version of the rule, whenever a per-repo cost happened to be injected, claimed that deleting the idle repository recovered its full standing charge. That attributed a shared account-level user fee to a single repository and asserted deletion reclaims it. Both counts are false, since the user remains active on other repositories and the fee continues unchanged. A cost recommendation is supposed to be a concrete, reclaimable dollar or nothing; there is no per-repo reclaimable dollar here, so the rule now ships nothing.

Why no other savings axis rescues it

Idle rules usually fall back to some lever: a rate delta, a schedule, a tier change. A Git repository has no compute to schedule, no SKU to downsize, and no storage tier to shift. An idle repo’s storage almost always sits inside the per-user free allowance anyway, so even the storage line is unattributable at the margin.

Hygiene is still yours to do

None of this means dead repositories are fine. They clutter discovery, confuse new joiners, and occasionally hold secrets in history. The cleanup case is organisational, not financial. Find candidates yourself:

Terminal window
aws codecommit list-repositories --query 'repositories[].repositoryName' --output text \
| tr '\t' '\n' | while read r; do
aws codecommit get-repository --repository-name "$r" \
--query 'repositoryMetadata.[repositoryName,lastModifiedDate]' --output text
done

Sort by the date column and archive or delete what nobody has touched in a year, but do it knowing the invoice will not move, which is exactly what this rule refuses to pretend otherwise about. AWS has also closed CodeCommit to new customers, so long-term consolidation onto another Git host is the direction most cleanups should point.

See it fire on your bill.

Connect an account read-only. The first findings land in minutes.

417 rule families across 353 resource types on 22 platforms. Every threshold, metric, and IAM action is documented on these pages before you grant anything.

417 rule families documented
353 resource types covered
read-only default access level
Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·