terraform-website VS former2

In 2017, after the provider-split in terraform 0.10, the docker provider was more or less abandoned and not actively maintained. We started contributing small features and bug fixes so we could use them in our deployment pipelines. We got in touch with several core contributors and began asking questions about the internals, especially about extending terraform, and how to write providers correctly. At that time, the documentation was still a work in progress, and for edge cases, there were no examples in the documentation yet. We started filing pull requests to update the documentation for this.

I'd create the issue here: https://github.com/hashicorp/terraform-website

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.

More info: https://github.com/iann0036/former2

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.

Author of Former2 here.

I've heard of a few people setting up pipelines that use the CLI with the `ALL` services option to generate inventories of their systems, but the generated template would almost certainly not work out of the box due to:

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