Have any questions about this process?
Get in touch today to talk to our experts about your migration from AWS CodeCommit.
Am I impacted? AWS CodeCommit migration guide
Share on socials
Am I impacted? AWS CodeCommit migration guide
Jason Spriggs
18 March 2025
3 min read
Jason Spriggs
18 March 2025
3 min read
AWS is shifting focus from CodeCommit. Read our guide to assess your situation and plan a smooth migration.
AWS CodeCommit, a fully managed source control service, has long been a staple for teams to host secure and scalable Git repositories. It facilitates code collaboration, change tracking, and version management without the burden of managing on-premises infrastructure.
However, AWS is shifting its focus and resources and de-emphasizing CodeCommit. While not outright deprecating until July 2025, AWS is investing less in new features and updates for CodeCommit. This means users might encounter limitations in the future, and it's crucial to evaluate whether this shift impacts your workflow. As part of our effort to help customers migrate from AWS CodeCommit to alternative solutions like GitLab, this guide provides a comprehensive approach to identifying your reliance on AWS CodeCommit and offers actionable steps for a smooth transition.
What this guide helps you achieve
Identify CodeCommit repositories
This guide provides clear instructions on how to list all existing CodeCommit repositories in each AWS region using the AWS CLI or the AWS Management Console.
Facilitate detailed analysis
The information gathered about your repositories (e.g., repository names, sizes, last activity dates) can be sent to our Solution Engineering team for a thorough analysis. This analysis helps in project planning, resource allocation, and identifying potential migration challenges. We will analyse repository activity, integration points, and team dependencies to provide a tailored migration strategy.
Plan your migration
Based on the analysis, we'll help you create a detailed migration plan that includes timelines, resource requirements, and potential risks.
Do I use AWS CodeCommit?
When verifying whether your organisation uses AWS Codecommit, you'll want to check whether any data exists within CodeCommit repositories and whether your teams are accessing it (or if it's been potentially abandoned). Below, we've provided two scripts to help you determine if your teams are likely impacted and how urgently your migration needs to occur.
Note: You'll need to run this script in each AWS account you’d like to scan. It will not cross the account boundary and run across an AWS Organisation.
Checking if you have any data in CodeCommit
The below "one-liner” script does the following:
- Gets a list of all AWS regions enabled for your account.
- In each region, checks to see if there are any CodeCommit repositories.
- For each CodeCommit repository found, pulls high-level metadata regarding each repository.
One-liner script
aws account list-regions --output text | grep ENABLED | cut -f2 | while read x ; do aws codecommit list-repositories --region $x --output text | grep REPOSITORIES | cut -f 3 | while read y ; do aws codecommit get-repository --repository-name $y --region $x --output text | sed -E 's/\s+/,/g' ; done ; doneGenerally, the script will take less than a minute to run, however, it may be longer depending on the number of repositories in CodeCommit. This script will output in CSV format that contains, per line:
- The ARN of the repository found
- The AWS Account ID the repository is in
- The URL of the repository
- The SSH git repository address
- When the repository was created
- What AWS KMS key is encrypting the repositories contents
- When the repository was last updated
- A UUID of the repository
- The name of the repository
This script can be run either in the Bash shell with the aws-cli installed, or within the AWS Console directly for the account you’re trying to analyse by using the AWS CloudShell console by clicking the CloudShell icon in the toolbar.
Checking for recent CodeCommit events/access
Another good thing to check for is if your CodeCommit repos, if determined you have some above, are actively being used in some way. Generally, the best way to do this is with either AWS CloudTrail or by creating a monitor within Amazon EventBridge. AWS provides a guide on understanding CodeCommit specific CloudTrail events here, and a guide similarly on Amazon EventBridge CodeCommit events here.
What does this mean for me?
Understanding your dependency on AWS CodeCommit is the first step in adapting to AWS's evolving service landscape. By following the steps outlined in this guide, you can effectively assess your current usage and plan for a seamless transition.
For example, if your team heavily relies on CodeCommit for CI/CD pipelines, you'll need to plan how those pipelines will be updated to use a new repository. Or, if multiple teams collaborate on shared CodeCommit repositories, you'll need to coordinate the migration to minimise disruption.
Why consider GitLab (or another alternative)?
While AWS CodeCommit is being de-emphasized, your DevOps environment doesn’t have to be disrupted. This transition presents an opportunity to evaluate and potentially enhance your source control systems. GitLab, for instance, offers advanced features like integrated CI/CD, issue tracking, and a comprehensive DevOps platform, which can significantly improve collaboration and efficiency.
Expert migration services
Adaptavist offers expert migration services to help you find the best alternative. Our team of specialists is ready to guide you through a seamless transition and optimise your DevOps environment. We provide end-to-end support, from initial assessment to post-migration support.
FAQs
What are the costs associated with migrating to GitLab?
Costs vary depending on the size and complexity of your repositories. Contact us for a personalised cost estimate.
Will there be downtime during the migration?
Our migration process allows for both systems to exist simultaneously until your team is ready for the cutover, allowing for the smallest amount of downtime for your team on your own schedule.
Contact Adaptavist now to get started on your migration journey.
Don’t let these changes catch you off guard—take action today to ensure your development processes remain uninterrupted.
Written by
Consulting Team Lead
Jason, an award-winning DevOps consulting team lead, providing architectural vision and technical expertise. At Adaptavist, Jason and his team implement a wide range of industry-leading technologies and processes for clients.