All Services

Developer Tools

AWS CodeCommit

AWS CodeCommit is a managed private Git repository service integrated with IAM, KMS, CloudTrail, approval rules, and event-driven notifications; after a temporary 2024 restriction, AWS reopened it to new customers on November 25, 2025.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with AWS CodeCommit.

Service availability and active-user cost

AWS CodeCommit Pricing & Availability Status

Check availability before cost. AWS states that CodeCommit is no longer available to new customers and that existing customers can continue using it as normal, so an account with no repositories today should plan around a different Git host.

Official AWS sources reviewed 2026-08-29.

Can I still use AWS CodeCommit?

AWS states that CodeCommit is no longer available to new customers, while existing customers can continue to use the service as normal. Accounts without existing CodeCommit usage should choose another Git provider rather than designing new pipelines around it.

Official AWS CodeCommit pricing and availability notice

How is CodeCommit priced for existing customers?

Billing is per active user per month. An account gets five active users free each month within stated limits, and each additional active user is a flat monthly charge that includes storage and Git request allowances. There are no upfront fees or commitments.

AWS CodeCommit user guide

How do I migrate a CodeCommit repository?

Mirror the repository with full history and all branches and tags to the new remote, then move everything wired to it: CodePipeline sources, build triggers, notification rules, and the IAM policies granting repository access. AWS documents a migration path to another Git provider.

Migrating a CodeCommit repository to another Git provider

Related AWS services for this plan

  • AWS CodePipeline — Repoint CodePipeline source stages first, since they hold the repository and branch references.
  • AWS CodeBuild — CodeBuild projects reference the source repository and its credentials, so update them with the pipeline.
  • AWS Identity and Access Management — Repository access is granted by IAM policies that must be replaced with the new provider's model.
  • AWS Key Management Service — CodeCommit repositories are encrypted with KMS keys that stay billed until the repository is removed.

AWS CodeCommit pricing and cost programs

Pricing model: Repository user and storage usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Active users · Storage · Git requests · Data transfer

Programs and modes: Source repositories · Approval rules · Notifications

CodeCommit availability for new customers and current allowances must be checked on the official page.

Free Tier: Available — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement AWS CodeCommit?

  • Hosts private Git repositories without operating source-control servers, storage, backups, or availability infrastructure.
  • Uses IAM and repository policies for access and integrates with KMS, CloudTrail, EventBridge, SNS, CodeBuild, and CodePipeline.
  • Supports pull requests, comments, branch controls, approval-rule templates, commit visualization, and repository triggers.

How to implement AWS CodeCommit

  1. Confirm CodeCommit fits the organization's source-hosting roadmap, create repositories with tags and an approved KMS key, and define branch, contributor, reviewer, and administrator roles.
  2. Configure HTTPS Git credentials, credential helper, or SSH without sharing identities; add approval rules and explicit branch protections through IAM; connect events to review and pipeline workflows.
  3. Test clone, push, pull request, approval, merge, backup or migration, and incident-revocation paths; monitor CloudTrail and repository events and periodically remove stale credentials and permissions.

AWS CodeCommit best practices

  • Use federated, individual identities and least privilege, deny direct changes to protected branches except through controlled roles, and require independent review for sensitive repositories.
  • Do not store credentials or generated secrets in Git; enable secret and dependency scanning in the delivery workflow and maintain a tested repository export or migration plan.
  • Treat service lifecycle as an architecture input: CodeCommit is currently available to new customers again, but verify the current AWS history and feature roadmap before a new strategic adoption.

AWS CodeCommit use cases and server impact

  • Private Git repositories governed by IAM
  • Source triggers for AWS-native pipelines
  • Cross-account infrastructure and application source control

Replaces self-managed Git servers and their storage and availability operations, while code review, branch governance, scanning, backups or migration planning, and developer identity remain yours.

Official implementation resources

Commonly paired AWS services