AWS recently announced that the managed source control service AWS CodeCommit is again generally available and that new features, including Git Large File Storage, will be added early in 2026. This marks a shift for the cloud provider that previously announced the service would not be further developed, closed it to new accounts, and encouraged migration to external alternative services.
In the “Future of AWS CodeCommit” article, Anthony Hayes announces that CodeCommit is open to new customers again and explains the shift:
We never stopped looking at the data or listening to you, and what you’ve shown us is clear: you need an AWS-managed solution for your code repositories. Based on this feedback, CodeCommit is returning to full General Availability, effective immediately.
Over a year ago, AWS announced a series of discontinuations and deprecations, as reported on InfoQ, and began posting articles to document how to replace it with third-party Git providers. The choice to no longer invest in CodeCommit has been the most contentious one, with developers confused about the status of the service and complaining about inconsistencies in AWS documentation and training materials: many projects were still using AWS CodeCommit even though some new users were not able to create a repository anymore.
While CodeCommit does not match the features of other code repositories, the managed Git service is critical in many AWS deployments, simplifying compliance in regulated industries thanks to the infrastructure within AWS boundaries. Furthermore, CodeCommit simplifies development through IAM integration, VPC endpoint support, and connectivity with continuous delivery service AWS CodePipeline and build service CodeBuild.
Monica Colangelo, AWS Hero and head of hyperscaler operations at ReeVo, explains why the decision matters to the community:
After months of conversations, feedback sessions, and honestly some moments of frustration wondering if any of it mattered, AWS just proved they were listening all along. CodeCommit is back, and it’s proof that customer voices actually shape decisions, even big ones, even reversals (…) To the AWS team: thank you for listening and for having the courage to course-correct.
Peter Bengtson, principal AWS cloud solutions architect at HiQ, is less convinced:
AWS suddenly resuscitating CodeCommit is like an ex who suddenly starts texting you about ‘getting together again’. The thing isn’t whether git exists in AWS or not. It’s the mindless vacillation (…) So, no, AWS. No way. You’ve lost my git trust.
In a popular “AWS CodeCommit is back from the dead” thread, the reaction of the community has been overwhelmingly positive, with user SharpCoder2890 commenting:
It would’ve been a nightmare for customers to migrate to other solutions. Even some AWS workshops were broken and needed tons of rework due to them moving off of CodeCommit.
Others are evaluating whether moving back to CodeCommit makes sense for projects that moved away. Discussing the planned Git LFS support, Hayes adds:
This has been your most requested feature. Git Large File Storage will enable you to efficiently manage large binary files like images, videos, design assets, and compiled binaries without bloating your repositories. You’ll get faster clones, better performance, and cleaner version history for large assets.
CodeCommit is currently available in 29 regions, with the cloud provider planning regional expansions in 2026, including Spain and Canada.
In a separate quarterly announcement, the cloud provider announced that different services are moving to maintenance mode, including S3 Object Lambda and Amazon CodeCatalyst, and others are now entering sunset, including AWS Proton.
