My IaC AWS Multi-Account Provisioning BluePrint & Best Practices…
<p>Onthis Article I will show you how to structure the IaC (Terraform) projects so they require no Value files (which usually tend to be scattered all over the place). I will also demonstrate how to use One single configuration file to rule all environments and How do I separate Platform and Application Infrastructure code.</p>
<h2>Topics in this Article:</h2>
<ul>
<li>Terragrunt as the Winner of the multi-account deployment tools</li>
<li>Terraform & Terragrunt working together</li>
<li>Application Infra Terragrunt Main Config file (Locals/Backend S3/AWS Provider)</li>
<li>AWS Identity Center (SSO) Permission Sets for Terraform Execution (Assuming Role with No long-living AWS Key and Secrets)</li>
<li>Platform vs Application Infrastructure</li>
<li>Platform Infra Terragrunt Main Config file (Locals/Backend S3/AWS Provider)</li>
<li>Creating the Terraform Execution Role (for Application Infra Deployment) with Trust Policy of an Role Provisioned with IAM Access Identity (SSO)</li>
</ul>
<p><a href="https://hector-reyesaleman.medium.com/my-iac-aws-multi-account-provisioning-blueprint-best-practices-4d18e280d403"><strong>Click Here</strong></a></p>
<p> </p>