AWS stops onboarding new customers to CodeCommit

2024-07-25 · Publisher : AWS · Domain : Cloud & DevOps

Since 6 June 2024, AWS no longer onboards new customers to CodeCommit, its managed Git service, which a migration guide to GitHub, GitLab or Bitbucket revealed in late July. AWS reverses the decision in November 2025.

### Background On 25 July 2024, the AWS DevOps blog publishes a guide to migrating AWS CodeCommit repositories to another Git provider. In the following days, the trade press notes that, since 6 June 2024, AWS no longer accepts new customers on CodeCommit (nor on Cloud9, SimpleDB, S3 Select, CloudSearch, Forecast and Data Pipeline). Existing customers keep using the service, but AWS says it does not plan new features. ### Key facts - Existing customers can keep using CodeCommit and create new repositories; only new accounts are refused. - The AWS guide covers migration to GitLab, GitHub, Bitbucket Cloud or any Git provider, using a mirror clone and push. - Communication was judged opaque: customers learned of the freeze through support posts, and some AWS Control Tower templates broke. - On 24 November 2025, AWS announces that CodeCommit returns to full general availability, with Git LFS support announced for Q1 2026 and new regions from Q3 2026. ### Why it matters The episode is a reminder that a hyperscaler's managed service can be sidelined without clear notice, leaving customers who invested in its integrations (IAM, CloudFormation) exposed. For consulting firms designing CI/CD chains on AWS, it argues for decoupling the code repository from the execution platform. The 2025 reversal also shows that demand for a cloud-managed repository carried weight. Affected teams had to choose between staying on the frozen service and migrating. ### Takeaway An AWS software engineering service frozen then rehabilitated: longevity risk applies to managed building blocks too.

Tags : AWS, CI/CD, DevOps, Hyperscaler