AWS Codestart and Codecommit - discontinued support

[bartoszbryk]

As of end of July 2024, AWS is ending support for both CodeCommit and CodeStar
Sources:
https://docs.aws.amazon.com/codestar/latest/userguide/transition-project-prod.html
https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/

Since any other VCS than Codecommit available in AFT use Codestar connection, this seems like a problem for using AFT further, or deploying new AFT modules

Please provide an alternative solution for AFT repositories or functional workaround

Currently it's not a problem for us, but not sure how the upgrades will behave

[akulbe-tnm]

It would be really nice if GitHub (and GitHub Actions) would get primary support.

[seansilvestri]

can we get some feedback from the team on this issue? This seems to be quite an important topic to address.
many thanks

[vivesan1]

Hi all, thank you for reaching out. AWS CodeCommit will no longer allow new customers to create repositories. However, existing AWS CodeCommit repositories will remain fully supported. Customers with existing AWS CodeCommit repositories can create new repos as well.
For connections with third party VCS providers, AFT leverages CodeStar Connections. Going forward, this functionality will be supported as CodeConnections, as mentioned here. The AFT team has a backlog item to switch to using the new CodeConnections APIs. Hope this helps!

[matthewbarreiro]

@vivesan1 are you able to share any kind of timeline on using the new CodeConnections APIs? A lack of support for GitLab (self-managed or hosted) is going to be a non-starter for some of my companies clients.

EDIT: We could work around this in the past by having GitLab push to CodeCommit, but that is no longer an option for new accounts.

[julianunespdedalus]

Hello everyone,

We were starting a Proof of Concept with the AFT for Terraform, but unfortunatelly we weren't able to finish a successfull deployment of the aws-control-tower-customizations Terraform Module.

It happens because after following all the mandatory steps (organization, new Landing Zones, Control Tower enablement and etc), we do not have the CodeCommit product available on our new accounts.

We did some diggering on the Terraform's Submodules, but it seems to only be allowing us to point to an existing Github Code Repository, and not to push the example pipeline's Terraform Code to a brand new repository (wich is what we were expecting, since it's the default behavior of the deployment on CodeCommit).

I would appreciate if someone could give us some guidance on how to have a similar deployment that used to work with CodeCommit, on Github (or any other VCS source, actually).

[wellsiau-aws]

@julianunespdedalus , sorry to hear the problem with CodeCommit.

have you tried to use the examples here https://github.com/aws-ia/terraform-aws-control_tower_account_factory/tree/main/examples to deploy it using an existing GitHub repository?

once you deployed the module, you need to complete post deployment steps: https://docs.aws.amazon.com/controltower/latest/userguide/aft-post-deployment.html

[wellsiau-aws]

CodeStar deprecation and support for CodeConnection is related to Terraform Provider AWS #36671

[hanafya]

AFT now supports GitLab and GitLab self-managed as version control systems (VCS) alternatives. Latest Release