aws-deployment-framework VS terraform-aws-control_tower_account_factory

In some scenarios you might have the need to replicate an AWS CodeCommit repository. When I was setting up a test organization using AWS Deployment Framework (ADF) I ran into this myself. Because I want to test the deployment of my landing zone I needed to have a close replica. This includes the CodeCommit setup. But at the same time I did not want to change the development workflow. The workflow is pretty straight forward. You create a feature branch to work in. When you are ready you merge it to a development branch. When it needs to go to production you merge it into the main branch. So we will use the development branch to deploy to the test organization. But, because the test organization is a replica of production. Merging to the development branch would not have effect on the test organization. For this we need to synchronize the development branch to the test organization.

Within AWS Organizations you can apply Service control policies (SCPs). All AWS Accounts under the OU (Organization Unit) with the SCP will be subjective to this SCP. What if you need to make a change in this SCP? How can you test this change? SCPs are not the only things you might want to test. Remember that I mentioned that ADF is also bootstrapping the accounts? That could be a VPC with subnets for networking. How do you ensure that the change that you made works as intended? When merging to your main branch. It will trigger a rollout process depending on your configuration.

AWS Deployment Framework (ADF)

Repos-AFT

I have raise the issue in here, you can check it out. https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/393

We're separating terraform infra gitops repo and application gitops repo with argo and Crossplane by setting the respective IRSA security boundaries for AWS EKS using custom Control Tower AFT deployment and sharing the respective cross-account resources with AWS RAM, so every developer gets it's own isolated EKS cluster inside an isolated account - there's no IAM Role per Developer nonsense.

Account Factory for Terraform

Control Tower Account Factory For Terraform — Setting up an AWS organisation isn’t easy, and when you try doing that with Terraform, it’s not any easier! You need to decide on things like patterns for your backend / state management (e.g. how many backend locations you want, and which AWS accounts those backends will live), and you’ll need to hand-roll a load of tooling to get things to work. This new module is kinda AWS out-of-the-box in a Terraform module. However… the code module behind the announcement only has only two contributors 👀. That said, it is nice to see AWS supporting Terraform more heavily. Earlier this year, AWS announced they would invest in officially supported Terraform modules [1][2], which now live under a new GitHub organisation called “AWS Integration & Automation” [1]. The terraform modules announcement did come with some criticisms, though about the lack of engagement with existing open source folks before announcing the project [1].