terraformer VS former2

‍Terraformer is a CLI tool developed by Google that generates Terraform files from existing infrastructure (reverse Terraform), simplifying the process of adopting Terraform in existing environments and speeding up the initial setup process. Terraformer supports multiple cloud providers, including AWS, Google Cloud, Azure, and others.

We had thought about the ability to convert HCL to Go, but not much thought in querying existing infra to generate HCL (like terraformer). If you want to experiment building on top of Lingon then please go ahead! I’d be happy to help provide the context from Lingon.

I haven't worked with any of the ones that purport to work with AWS, but a quick Google shows terraformer and Terracognita as options - maybe look into trying those out?

This maybe a bit more complicated if you're not into coding/terraform but I'd use terraformer to convert all of your infrastructure from implementation to code while in AWS, then switch providers and with a bit of jiggly of the code implement your infra into gcs as IaC and keep it that way if/when you switch again.

I've been wondering if this tool is any good. https://github.com/GoogleCloudPlatform/terraformer/blob/master/docs/aws.md

If you've to write the code (I assumed you just needed to reorganize it without TG) maybe consider https://github.com/GoogleCloudPlatform/terraformer

Have you taken a look at https://github.com/GoogleCloudPlatform/terraformer?

https://github.com/GoogleCloudPlatform/terraformer supports multiple platforms. But I’m pretty sure, that the code this tools produces is not something you want to maintain in the future. If you decide to go this route, you will have to refactor afterwards. In my opinion, this is so much work, you might as well just write your own code and use terraform import for each resource.

Former2 is a tool that automates the creation of Infrastructure-as-Code (IaC) scripts from existing AWS resources. It utilizes the AWS JavaScript SDK to scan the user’s AWS infrastructure, identifying all available resources. Users can then select from this list which resources they want to include in their IaC outputs. This process simplifies the task of writing IaC scripts, especially for complex environments, by directly converting current AWS configurations into ready-to-use code. Former2 is particularly useful for documenting existing infrastructure or for migrating manually created resources into an IaC framework.

You can use tools like https://github.com/cycloidio/terracognita or https://github.com/iann0036/former2 to generate the terraform code for you. Then you can consolidate them and if they are simply the same type of objects with different values then you can use terragrunt to pass values to your terraform module.

I have never tried out this tool, but maybe it's worth checking: you could create all the stuff via AWS Console in a sandbox environment and then try to use former2. Nothing autogenerated will ever be good enough compared to handcrafted, but it should give you a nice starting point without much effort.Such a tool can not be expected to work reliably. Thankfully, you need to cover only classic, foundational services like EC2, ELB, and IAM, so I would expect them to work properly for those use cases.

Not quite: a command line tool is also available: https://github.com/iann0036/former2/blob/master/cli/README.md

https://github.com/iann0036/former2

This will scan your entire account and list all of your resources - it's actually made for generating CloudFormation templates, but it's very useful for a use-case like yours.