AWS CodeCommit is fully back to GA. I tested creating a repository in 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 had previously been announced as "De-emphasized."
With this announcement, onboarding of CodeCommit for new AWS accounts (new customers), which had been restricted until now, has been immediately resumed.
In this article, I'll review the update overview and verify using AWS CLI whether repository creation is now possible with "a new account created just last month."
Update Overview
According to the official blog, since the de-emphasis announcement in July 2024, many customers provided feedback that "CodeCommit is an essential part of their infrastructure." In particular, AWS native features such as IAM integration, VPC endpoint support, and CloudTrail logging were reassessed as being difficult to replace in regulated industries and AWS environment development.
Key changes include:
- Resumption of new customer acceptance: New accounts can now create repositories via console, CLI, and API.
- Publication of roadmap: Investment will continue beyond mere maintenance.
- Git LFS support: Planned for Q1 2026
- Regional expansion: Phased rollout beginning Q3 2026 (including eu-south-2, ca-west-1, etc.)
Test Environment
For this verification, I used an AWS account created during the period when new CodeCommit usage was restricted.
Confirming Account Creation Date
First, to confirm this environment is a "new environment with no previous CodeCommit usage history," I checked the creation date 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 was created on May 27, 2025. This was after the July 2024 CodeCommit reduction announcement, and under the previous policy, creating new CodeCommit repositories would not have been possible with this account.
Repository Creation Verification Using AWS CLI
Now, let's attempt to create a repository using AWS CLI.
Command Executed
I executed 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
The command executed without errors and returned the repository metadata as shown below:
{
"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:
2025-11-24T21:14:59(immediately after the announcement) - Clone URL: Both HTTPS and SSH URLs were properly issued
- Repository ID: A new UUID was assigned
This confirms that accounts created during the de-emphasis period can now create and use CodeCommit resources without issue.
Summary
I confirmed AWS CodeCommit's return to GA status and the ability to create repositories in new accounts.
While many may have considered migrating to alternatives, CodeCommit remains a powerful option for cases requiring closed network configuration within VPC and strict access control via IAM. I look forward to upcoming feature enhancements, including the planned Git LFS support.
Reference Links
