ACAI Lab – IaC Provisioning
The following blog post is about AWS Landing Zone Provisioning – the native way.
The focus of the post lies on provisioning AWS accounts of the ACAI AWS Foundation Lab, utilizing Terraform which is the de facto standard for infrastructure as code (IaC).
Depending on the architecture style each solution has a different IaC footprint (purple section):
We designed the IaC CI/CD pipelines to consist of an AWS CodeCommit Repository and an AWS CodePipeline. The CodePipeline performs Terraform Plan and Terraform Apply in two AWS CodeBuild steps. Optionally a manual approval step between plan and apply can be added.
It is good practice to have dedicated AWS accounts per solution operated in the cloud.
In our ACAI AWS Foundation Lab each AWS account has two IaC CI/CD pipelines – one for the Foundation Baseline (shared over all AWS accounts) and one for the account resources. This leads to many IaC CI/CD pipelines.
In the lab setup the IaC CI/CD pipelines are hosted in the Core IaC Provisioning account (Link to Core Provisioning). The Core IaC Provisioning account itself is also managed via Terraform.
Advantages of this architecture
- no credentials to access target accounts – no key rotation required
- segregation of Foundation Baseline and access account resource CI/CD pipelines
- fully AWS native IaC CI/CD pipelines – no expensive license cost
We are ACAI Consulting – specialized in AWS Multi Account Security and Governance.
If you have any questions, feel free to get in touch with us: firstname.lastname@example.org