AWS CodeCommit Deprecated - Easy Migration to TaraVault Git

August 5th, 2024 by inflectra

Amazon Web Services (AWS) announced on July 25th, 2024 that it is deprecating AWS CodeCommit, and advising its customers to migrate to an alternate Git platform. Many of our customers use AWS services including CodeCommit, and have been asking us for alternatives. In this article we describe the recent AWS news and outline how you can easily migrate your AWS CodeCommit repositories to Inflectra TaraVault and also integrate other AWS code offerings such as CodeBuild and CodePipeline.

What was AWS CodeCommit?

AWS CodeCommit was a fully managed source control service that made it easy for teams to host secure and scalable Git repositories in AWS. AWS CodeCommit had the following features:

Managed Service: AWS CodeCommit eliminated the need to operate your own source control system or worry about scaling its infrastructure.
Secure: CodeCommit repositories were encrypted at rest and in transit. You could also control who can access each repository using AWS Identity and Access Management (IAM).
Integrated with AWS Services: CodeCommit integrated with other AWS services like AWS Lambda, AWS CodeBuild, AWS CodePipeline, and Amazon CloudWatch for a complete CI/CD workflow.
High Availability: The service was designed for high availability and durability.
Standard Git Commands: You could use the standard Git commands you are familiar with.

AWS CodeCommit was used by developers working heaving in the AWS environment, but never caught on in the wider DevOps community.

What is the Recent News?

AWS announced on July 25th that they were deprecating a set of lesser-used services, including CodeCommit:

After careful consideration, we have made the decision to close new customer access to AWS CodeCommit, effective July 25, 2024. AWS CodeCommit existing customers can continue to use the service as normal. AWS continues to invest in security, availability, and performance improvements for AWS CodeCommit, but we do not plan to introduce new features.

As part of the announcement, AWS provided guidance on how to migrate an AWS CodeCommit Git repository to another provider:

Customers can migrate their AWS CodeCommit Git repositories to other Git providers using several methods, such as cloning the repository, mirroring, or migrating specific branches. This blog describes a basic use case to mirror a repository to a generic provider, and links to instructions for mirroring to more specific providers. Your exact steps could vary depending on the type or complexity of your repository, and the decisions made on what and how you want to migrate. This post only describes how to migrate Git repository data, and does not describe exporting other data from CodeCommit such as pull requests.

What is TaraVault?

TaraVault is a source code management platform developed by Inflectra, which is designed to integrate seamlessly with their Spira development suite. It supports both Git and Subversion repositories, allowing teams to manage their source code within the same system they use for project management and application lifecycle management (ALM).

Key Features of TaraVault:

Integration with Spira: TaraVault is tightly integrated with SpiraTest, SpiraTeam, and SpiraPlan, Inflectra’s ALM tools. This integration provides code-level traceability, enabling users to link code commits with requirements, tasks, and issues in Spira.
Supports Multiple SCM Systems: Unlike AWS CodeCommit, which only supports Git, TaraVault supports both Git and Subversion, giving teams flexibility in their version control strategy.
Secure and Hosted: TaraVault offers a secure, cloud-hosted environment for managing source code, similar to CodeCommit, which removes the need for teams to manage their own source control infrastructure.
Free for Spira Customers: TaraVault is provided as a free service to customers who are already using Spira, making it a cost-effective option for teams that are already invested in the Inflectra ecosystem.

Why Choose TaraVault Over AWS CodeCommit?

Tight Integration with ALM: If your team is using Spira for project management and ALM, TaraVault’s integration offers a streamlined experience with features like traceability between code commits and project artifacts, which is not natively available in AWS CodeCommit.
Support for Subversion: If your team relies on Subversion or has a mixed environment with both Git and Subversion, TaraVault’s multi-SCM support could be a key differentiator.
Cost Considerations: For teams already using Inflectra's tools, TaraVault being free could be a more cost-effective choice compared to the usage-based pricing of AWS CodeCommit.

How to Migrate to TaraVault?

If you are interested in migrating from AWS CodeCommit to TaraVault, we have some handy instructions for you here: KB198 - How do I upload my existing Git repository?

Integrating Other AWS Code Products

AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. It's part of the Amazon Web Services (AWS), cloud computing platform.

AWS CodePipeline and AWS CodeBuild are both parts of Amazon Web Services' suite of developer tools, but they serve different purposes within the realm of continuous integration and continuous delivery (CI/CD).

SpiraTeam and TaraVault integrate seamlessly with the AWS Code tools in a variety of ways. You can easily configure your AWS CodeBuild projects to fetch code from a TaraVault Git repository, and report back against a SpiraTeam release by creating a new build each time they run. This lets you see the health of your CI/CD process within SpiraTeam. You can learn more about this integration in our whitepaper: DevOps Using SpiraTeam, TaraVault and AWS CodeBuild.