terragrunt-infrastructure-live-example VS terraform-example-foundation

In the official Terragrunt documentation there is a good article about how to set up a Terragrunt project and where to place modules. In fact, there is also a repository on GitHub providing an example project on how the creators recommend setting up Terragrunt. I certainly recommend going through that repository, because it is a good reference for a starting point. Having that said, I like to structure mine a little bit differently. My recommendation is to have different AWS accounts for each environment. Getting a new account usually is relatively easy to accomplish even if we are working in a corporate environment (your workplace most likely is using AWS Organizations to manage accounts). The existence of multiple accounts does not require additional costs, we only pay for what we use.

NOTE: More information about the terragrunt.hcl file can be found in this example repository.

Here's a pointer to an example repository with a Terragrunt monorepo (good, easy to manage), and each module called gets its unique statefile (good, smaller blast radius) where the tradeoff is learning a new tool and paradigm: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example.

I also highly recommend to check out how terragrunt recommends structuring your repo and even further details on this documentation page.

https://github.com/gruntwork-io/terragrunt-infrastructure-live-example/blob/master/_envcommon/mysql.hcl https://terragrunt.gruntwork.io/docs/features/keep-your-terraform-code-dry/

did you have a look at this example? https://github.com/gruntwork-io/terragrunt-infrastructure-live-example/blob/master/terragrunt.hcl

Terragrunt! Using a scaffolding approach like this for inspiration https://github.com/gruntwork-io/terragrunt-infrastructure-live-example

I would recommend taking a look at the example repo here: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example. The layout you have doesn't look like a structure that would work well with terragrunt.

A good example is in gruntwork-io / terragrunt-infrastructure-live-example repository and further documentation on Terragrunt's own documentation page.

- How do we secure?

You can use this approach for each step along the way, how to secure secrets in your cloud? code? IaC? container deployments? CI/CD?

If we assume infra / app is code, the tooling matters a lot less. How do you provision certificates via IaC? How do you grant IAM to resources and how do you revoke?

There are examples like https://github.com/terraform-google-modules/terraform-exampl... of more advanced IaC architectures, but you can start as small or as complex as you want and evolve if done properly.

Personally, I love me some Kubernetes + ArgoCD (GitOps) + Google Workload Identity + Google Secret Manager, but I am 100% biased.

Also looked for something similar, and unfortunately didnt find one. Based our enterprise repo off the caf model (not using the module) similar to this google repo: https://github.com/terraform-google-modules/terraform-example-foundation

How did I tackle this exam? 1. On github there is an example foundation for GCP on terraform. https://github.com/terraform-google-modules/terraform-example-foundation I went through this week after week to help me learn. I made customizations and I deployed and destroyed over and over again, making changes. I used this to create a basic organization with a website, this is how I learnt.

If you are looking to setup a new cloud project with Terraform, then that is an another thing. For GCP, Google offers a toolkit: https://github.com/terraform-google-modules/terraform-example-foundation

https://github.com/terraform-google-modules/terraform-example-foundation maybe have a look at the layer approach from Google?