AWS CodeCommit Fully Returns to GA: Testing Repository Creation with a New Account
This page has been translated by machine translation. View original
On November 24, 2025, AWS announced the full return to General Availability (GA) of AWS CodeCommit, which it had previously announced would be placed under a "De-emphasis" policy.
With this announcement, onboarding to CodeCommit for new AWS accounts (new customers), which had been restricted until now, has resumed immediately.
In this article, we review an overview of the update and, using an account created just last month, verify with the AWS CLI whether it is now possible to create a repository.
Update Overview
According to the official blog, since the deprecation announcement in July 2024, many customers have given feedback that "CodeCommit is an important part of our infrastructure." In particular, it was reassessed that AWS-native capabilities such as IAM integration, VPC endpoint support, and CloudTrail logging are difficult to replace in regulated industries and for development within AWS environments.
The main changes are as follows.
- Resumption of accepting new customers: Repositories can now be created in new accounts via the console, CLI, and API.
- Roadmap published: Investment will continue rather than mere maintenance.
- Git LFS support: Planned for Q1 2026
- Region expansion: Gradually from Q3 2026 (eu-south-2, ca-west-1, etc.)
Verification Environment
For this verification, we used an AWS account that was created during the period when new use of CodeCommit was restricted.
Checking the Account Creation Date
First, to confirm that this environment is a "new environment with no prior CodeCommit usage history," we checked the creation date and time of the oldest IAM role.
$ aws iam list-roles --query 'Roles[?RoleName==`AWSServiceRoleForSupport`].{Name:RoleName,CreateDate:CreateDate}'
[
{
"Name": "AWSServiceRoleForSupport",
"CreateDate": "2025-05-27T03:05:20+00:00"
}
]
As shown in the log above, this environment's account started being used on May 27, 2025. This is an environment created after the July 2024 announcement of CodeCommit's scale-down, and under the previous policy, this account should not have been able to create new CodeCommit repositories.
Repository Creation Verification with the AWS CLI
Now, let's actually try creating a repository using the AWS CLI.
Command Executed
We ran the following command to create a repository named test-repo.
aws codecommit create-repository \
--repository-name "test-repo" \
--repository-description "Test repository" \
--region us-east-1
Execution Result
As a result of running the command, no error occurred, and the repository metadata was returned as follows.
{
"repositoryMetadata": {
"accountId": "123456789012",
"repositoryId": "e20c0c4a-c073-4da7-a029-10868fbf3957",
"repositoryName": "test-repo",
"repositoryDescription": "Test repository",
"lastModifiedDate": "2025-11-24T21:14:59.123000+00:00",
"creationDate": "2025-11-24T21:14:59.123000+00:00",
"cloneUrlHttp": "https://git-codecommit.us-east-1.amazonaws.com/v1/repos/test-repo",
"cloneUrlSsh": "ssh://git-codecommit.us-east-1.amazonaws.com/v1/repos/test-repo",
"Arn": "arn:aws:codecommit:us-east-1:123456789012:test-repo"
}
}
From the created repository information, the following facts were confirmed.
- Creation date and time:
2025-11-24T21:14:59(immediately after the announcement) - Clone URLs: HTTPS and SSH URLs were issued normally
- Repository ID: A new UUID was assigned
This confirmed on a real environment that even an account created during the deprecation period can now create and use CodeCommit resources without any problems.
Summary
We confirmed the return of AWS CodeCommit to GA and that repositories can be created in new accounts.
Many of you may have once considered migrating, but CodeCommit remains a powerful option in cases that require a closed network configuration within a VPC or strict access control via IAM. We will also keep an eye on future feature expansions, such as the planned Git LFS support.
Reference Links
