AWS Deprecates CodeCommit

Customers can migrate their AWS CodeCommit Git repositories to other Git providers using methods such as cloning, mirroring, or migrating specific branches. The process begins with ensuring the necessary credentials and permissions for both AWS and the target provider. Users can clone the repository from AWS CodeCommit to their local machine using the appropriate clone URL. For migration to GitLab or GitHub, users should follow the respective documentation for importing source code from a URL.

The generic migration process involves cloning the repository, setting up a new remote repository, and pushing the local repository to the new provider. It is important that the remote repository is empty and that any branch protections are disabled to allow for a successful push. After migration, users should verify that all files, branches, and tags have been transferred correctly.

If continuing to work with the migrated repository, users should update the remote URL to point to the new provider and adjust any CI/CD pipelines accordingly. It is also essential to inform team members about the migration and provide them with the new repository URL. Finally, users can delete the original AWS CodeCommit repository if no longer needed. The blog post provides additional resources for incremental migration and further guidance on repository management.