GitHub Enterprise: The best migration path from AWS CodeCommit

Last month, Amazon Web Services (AWS) announced that, effective July 25, 2024, it is no longer accepting new customers for AWS CodeCommit. While existing customers can continue to use the service with maintained security, availability, and performance, AWS will not introduce new features or accept new users.

If you’re an existing AWS CodeCommit customer or were considering it for your source code management, you likely have many questions about the impact of these changes and what it means for you. In this post, we’ll share how you can navigate through this change and why you should consider migrating to GitHub Enterprise.

What this change means for you

If you’re not an existing customer, simply, you will not have access to AWS CodeCommit and will need to consider alternative Git providers for your source code management.

If you are an existing AWS CodeCommit customer, you’ll have two options to consider:

1. Continue using AWS CodeCommit—with the understanding that AWS will not introduce new features outside of ongoing investment in security, availability, and performance improvements. While you’ll avoid change and disruption, you’ll no longer receive any new product features while other solutions continue to innovate—which may have negative consequences in the longterm.
2. Migrate your AWS CodeCommit Git repositories to other Git providers—whether via cloning your repository, mirroring, or migrating specific branches. You’ll need to research and assess which platforms fit your specific requirements.

This is a critical decision that you’ll need to make to determine your best path forward for your software development needs.

Why you should consider GitHub Enterprise

GitHub is the world’s leading AI-powered development platform. With GitHub Enterprise, you’ll benefit from a unified, enterprise-grade platform to help you build, secure, and deliver software faster to unlock innovation at scale.

Key advantages of GitHub Enterprise:

• Unified, enterprise-grade development platform. The GitHub platform provides an extensive suite of developer tools, ensuring a seamless and efficient development process.
• AI-powered productivity. With GitHub Copilot, developers gain access to the world’s most trusted AI-powered coding assistant, enhancing productivity and collaboration.
• Robust security. GitHub Advanced Security (GHAS) offers native security tools to protect your code and workflows.
• Automated CI/CD. GitHub Actions enables automated CI/CD workflows, streamlining your development pipeline.
• Effective collaboration. Tools like GitHub Projects and GitHub Issues facilitate efficient project management and team collaboration.
• Hosted packages. GitHub Packages allows for easy hosting and management of packages.
• Preconfigured environments. GitHub Codespaces provides prebuilt and configured development environments, ready for immediate use.

With a community of over 100 million developers, we are dedicated to delivering exceptional experiences that meet the diverse needs of software development. Supported by cutting-edge, AI-powered technologies and a global, interconnected community, we strive to provide the tools and support necessary for innovation and success.

Migrating your AWS CodeCommit Git repository to GitHub

Migration planning can feel overwhelming. To help you through the planning and execution of your migration, we have detailed documentation, import tools, and comprehensive support to help you navigate this process.

As stated in AWS’s announcement, you’ll need to complete a couple prerequisites prior to migration.

1. Before you can migrate your CodeCommit repository to another provider, make sure that you have the necessary credentials and permissions to both the AWS Management Console and the other provider’s account. For migrating to GitHub, use CodeCommit static credentials as described in HTTPS users using Git credentials.
2. In the AWS CodeCommit console, select the clone URL for the repository you will migrate. The correct clone URL (HTTPS, SSH, or HTTPS (CRC)) depends on which credential type and network protocol you have chosen to use.

We also offer additional expert services for those complex migration scenarios to help support your migration experience.

Migrating your CI/CD workflows

Depending on the CI/CD tool that you’re using with AWS CodeCommit, you may be able to continue with what you’re already using, or you may need to migrate to a new tool.

GitHub Actions is our integrated CI/CD automation workflow tool, included in GitHub Enterprise. GitHub Actions integrates seamlessly with your GitHub repository, allowing you to automate workflows from code review to deployment. It supports custom workflows, a vast marketplace of pre-built actions, and multiple environments, making it a versatile and secure choice for your CI/CD needs.

If you’re using another CI/CD tool like CircleCI, Travis CI, or Jenkins, GitHub supports many of these third-party solutions for your CI/CD workflows.

Third-party tools and integrations

Development teams use many integrations as part of their day-to-day software development workflow. These might be third-party integrations or custom integrations built internally using publicly available APIs. GitHub has an extensive ecosystem and APIs to help support your workflows.

Explore the GitHub Marketplace to find the tools and extensions you need.

If your team has built custom API integrations, you’ll need to analyze and assess your needs and utilize the GitHub API to build and extend these.

Want to try GitHub Enterprise first?

If you want to experience GitHub Enterprise before committing to migrating, try a 30-day free trial of GitHub Enterprise to explore for yourself before you make a decision.

Written by

Melody Mileski

@mmileski

Jun Pak

@jyoungpak

Product Marketing Manager, GitHub