AWS CodeCommit Repository
Does ZopNight manage AWS CodeCommit Repository?
CodeCommit bills per active user per month beyond the first 5, with overage charges for storage and Git requests, and AWS has closed the service to new customers. ZopNight inventories repositories on the 6-hour cycle, tracks cost from Cost Explorer or CUR 2.0, and flags inactive repositories worth migrating or archiving.
Rules that fire on AWS CodeCommit Repository
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery, cost tracking, and recommendations only. |
AWS CodeCommit hosts private Git repositories, billed per active user per month plus storage and request overages. Inactive repositories and departed-user allocations keep small charges recurring, and the service’s deprecation for new customers makes inventory worthwhile.
Seats, storage, and a sunset
CodeCommit’s meter is the active user: the first 5 each month are free, each additional one bills monthly, and every active user carries an allowance of storage and Git requests with per-GB and per-request overages beyond it. “Active” includes anything authenticating as a user, including CI systems and service roles hitting the repos, which is how accounts end up paying for more seats than they have engineers. Overlaying all of it: AWS closed CodeCommit to new customers in 2024, so every repository still here is on borrowed architectural time.
Inventory ahead of the exit
ZopNight discovers repositories through a dedicated provider on the 6-hour cycle and tracks CodeCommit cost from Cost Explorer or CUR 2.0. The hygiene recommendation flags inactive repositories (no pushes, no clones worth the name) as candidates for archiving or deletion, and the deprecation context sharpens the finding: an inactive CodeCommit repo is not just a small recurring charge but migration debt that gets harder to pay down as institutional knowledge of the service evaporates.
The slow leak pattern
Departed engineers’ credentials linger in IAM and keep counting as users when automation runs under them. Mirror repositories created for a one-time GitHub migration keep receiving mirror pushes long after the migration finished, counting as active users forever. And per-project repos from CodePipeline tutorials sit with a single initial commit, individually free, collectively an unmapped corner of the account.
Taking stock in the console
The CodeCommit console lists repositories with last-modified dates, which separates the living from the archived-in-place. For anything active, the practical question is migration destination and timeline; for everything else, an export to S3 or a push to the organization’s current Git host closes the account’s dependence on a sunsetting service.