cloudparts

AWS CodeCommit

AWS’s managed Git hosting: private repositories inside an AWS account, with access controlled by IAM instead of separate user accounts, pull requests with approval rules, and triggers into other AWS services.

What it is
Version control
Type
Managed service on AWS
Made by
Amazon Web Services
License
Proprietary
Facts checked
20 October 2026
Website

What it is

A CodeCommit repository lives in one AWS Region of one AWS account, and clients use ordinary Git over HTTPS or SSH. It has no user accounts of its own: every request is an AWS identity checked by IAM. An IAM user can have Git credentials or an SSH key, and roles, federated users and temporary credentials connect through git-remote-codecommit, a Git helper that uses your AWS CLI credentials instead of a Git password, with URLs like codecommit::us-east-1://shop. IAM policies grant actions such as codecommit:GitPush on a repository’s ARN, and can limit pushes and merges to particular branches. Data is encrypted with AWS KMS, with an AWS managed key or, since December 2023, a customer managed key.

On top of Git it adds pull requests, comments and approval rules, which can be attached to many repositories at once through templates; triggers that send push events to Amazon SNS or AWS Lambda; and a source action for CodePipeline and CodeBuild. The quotas: 5,000 repositories per account (25,000 on request), up to 2 GB per Git blob, 1,000 open pull requests, and no limit on total repository size, though AWS suggests Amazon S3 for large files that change often.

Pricing is per active user, meaning any IAM user, role or federated identity, including the roles CodeBuild and CodePipeline use, that touches the service in a month. The first five are free, with 50 GB of storage and 10,000 Git requests a month; each further user costs $1 a month and adds 10 GB and 2,000 requests. AWS closed CodeCommit to new customers on July 25, 2024, then returned it to general availability in November 2025 in 29 Regions, promising Git LFS for the first quarter of 2026 and two more Regions from the third quarter. As of October 2026 the user guide lists no LFS launch, and its Region list still has the same 29.

Why teams pick it

  • No separate user directory: access uses IAM users, roles and temporary credentials, activity is logged in CloudTrail, and VPC endpoints keep traffic off the internet
  • Very cheap for small teams: five active users free, then $1 per user per month
  • Fits AWS automation: push events go to Lambda or SNS, and CodePipeline and CodeBuild read from it directly
  • No limit on repository size or count beyond the account quota, backed by a 99.9% uptime SLA

Watch out for

  • An uncertain track record: it spent 16 months closed to new customers before AWS reversed course and apologized
  • Repositories, branches, commits and pull requests only: issue tracking and CI come from other tools, and Git LFS, promised for early 2026, had not shipped by October 2026
  • Each repository is tied to one Region, and federated users need the git-remote-codecommit helper, which some IDEs don’t support
  • Files added through the console, API or CLI rather than Git are limited to 6 MB each

Alternatives

What all version control have in common →Compare side by side →
Azure ReposAzureMicrosoft’s hosted Git repositories, part of Azure DevOps: pull requests guarded by branch policies that can require reviewers, linked work items and a passing build, plus the older centralized Team Foundation Version Control.Secure Source ManagerGoogle CloudGoogle Cloud’s managed Git forge: each customer gets its own single-tenant instance in one region, with repositories, pull requests, issues and branch protection, all behind Google Cloud IAM and private networking.

How it fits with other technologies

Create a repository, clone it with temporary credentials and open a pull request · bash

aws codecommit create-repository --repository-name shop --repository-description "Web shop"

pip install git-remote-codecommit       # uses your AWS CLI credentials, no Git password
git clone codecommit::us-east-1://shop && cd shop

git switch -c fix-login
git commit -am "Extend login session timeout"
git push -u origin fix-login

aws codecommit create-pull-request --title "Extend login session timeout" \
  --targets repositoryName=shop,sourceReference=fix-login,destinationReference=main

See it in a real stack

No architecture uses AWS CodeCommit yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2014–2025

AWS announced CodeCommit at re:Invent on November 12, 2014, alongside CodeDeploy and CodePipeline, as a managed service that hosts Git repositories and works with all Git tools. The pitch was safety for source code as valuable intellectual property: files encrypted when checked in, and access controlled with IAM. It became generally available on July 9, 2015, in US East (N. Virginia) only, at $1 per active user per month with no limits on repository size or file count. Triggers on push and CloudTrail logging were still on the to-do list.

Over the next five years it filled in those gaps: triggers to SNS and Lambda in 2016, pull requests in November 2017, branch-level permissions in May 2018, VPC endpoints in March 2019, approval rules in November 2019 and git-remote-codecommit for federated access in March 2020, while it spread to 29 Regions. Customer managed encryption keys followed in December 2023.

On July 25, 2024 AWS stopped accepting new customers and published a guide to migrating repositories to other Git providers. On November 24, 2025 it reversed course and returned CodeCommit to full general availability, saying customers had told it they need an AWS-managed home for code and valued its IAM integration, VPC endpoints, CloudTrail logs and connections to CodePipeline and CodeBuild, especially in regulated industries. AWS apologized for the uncertainty and published a roadmap starting with Git LFS.

Why it’s built this way

IAM instead of its own users
Using the identities and policies an AWS account already has means no second user directory, credentials that can be temporary, and the same audit trail as every other AWS API.
Encrypt every repository
AWS framed source code as valuable intellectual property, so repositories were encrypted at rest from launch, today with AWS KMS keys that customers can manage themselves.
Charge per active user, not per repository
At launch each active user cost $1 a month and brought an allowance of storage and Git requests, with no limit on the number or size of repositories, so teams could split code freely.
Bring it back instead of retiring it
After closing it to new customers, AWS heard that regulated customers in particular wanted their code to stay in an AWS-managed service tied to IAM, CloudTrail and VPC endpoints, and reopened it.

Timeline

  1. 2014

    Announced at re:Invent (November 12)

  2. 2015

    Generally available in US East (N. Virginia) (July 9)

  3. 2017

    Pull requests (November 20)

  4. 2019

    VPC endpoints (March 7) and approval rules (November 20)

  5. 2024

    Closed to new customers (July 25)

  6. 2025

    Returns to general availability (November 24)

Sources11 · facts checked 20 October 2026

Improve this page on GitHub