Using Terraform Workspace for AWS multi account archtetctures

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

AppSignal knows why the f*#k it crashed.
Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
www.appsignal.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  1. terraform-workspaces-aws-multi-account

    Building and managing AWs multi account architecture with Terraform workspaces.

  2. AppSignal

    AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.

    AppSignal logo
  3. terraform-best-practices

    Terraform Best Practices free ebook translated into 🇬🇧🇦🇪🇧🇦🇧🇷🇫🇷🇬🇪🇩🇪🇬🇷🇮🇱🇮🇳🇮🇩🇮🇹🇯🇵🇰🇷🇵🇱🇷🇴🇨🇳🇪🇸🇹🇷🇺🇦🇵🇰 (by antonbabenko)

    I generally consider the AWS CLI configuration to be something that's unique to a developer's workstation, and shouldn't be referenced in terraform code (in the form of tying the workspace name to your AWS profile name).

    This would only work if all developers on a team have synchronised the same AWS CLI config (which to me is like asking people to synchronise dotfiles, not something I'd be willing to do).

    My go-to architecture for multi-environment tends to be this, as it lends itself relatively well to Git Flow (or GitHub Flow): https://github.com/antonbabenko/terraform-best-practices/tre...

  4. configure-aws-credentials

    Configure AWS credential environment variables for use in other GitHub Actions.

    The AWS SDK supports supplying credentials based on environment variables. When on my workstation I set AWS_PROFILE to select what profile I'm using, prior to running Terraform. This is then portable to CI where we may be using something like https://github.com/aws-actions/configure-aws-credentials to assume a role rather than using a pre-configured CLI profile.

  5. terraformer

    Discontinued CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code

    The Terraformer tool was the biggest blessing when I had to reverse engineer our AWS stack into .tf modules.

    Shoutout to the Waze team for creating it!

    https://github.com/GoogleCloudPlatform/terraformer

    We built out a large serverless stack on AWS, and we got a request from higher ups to convert it all into Terraform modules for portability and transparency purposes.

    The Terraformer tool pulled in the entire stack and spit out the whole thing into tf files in less than 30 seconds.

    Everyone was super impressed on the team lol.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Choose IaC wisely the first time: CloudFormation, Terraform and pain

    2 projects | dev.to | 26 Jun 2025
  • Terraformer: Convert Existing Infrastructure to Code with Ease

    1 project | news.ycombinator.com | 1 Oct 2024
  • Automate Gitlab Repository Settings with Terraform

    2 projects | dev.to | 13 Jul 2024
  • Terraformer + refactoring with 'moved' blocks

    1 project | /r/Terraform | 23 Jul 2023
  • How do you glue Terraform resources together?

    1 project | /r/devops | 4 Jun 2023

Did you know that HCL is
the 22nd most popular programming language
based on number of references?