terraforming VS aws-toolkit-vscode

Terraforming

I would also strongly recommend an iterative triage process: don't feel that you need to solve everything all once. It's a huge amount of progress if you can get to a stage where you understand the relationships between services, have enough monitoring to identify failures, and can iteratively move services to more granular IAM policies even if it's all still running in one big account. Simply using a tool like terraformer or terraforming to move the manual configuration into an IaC workflow is an accomplishment, especially since it helps you both make changes more confidently and identify where new changes are still being made. Depending on the politics, that last part might be important: you'll be unpopular if you take away everyone's rights but you'll probably have better luck first nudging people to make them using a sensible flow rather than by hand.

Haven't tried this but if I ever find myself in your situation I'll give it a spin https://github.com/dtan4/terraforming

There are a couple of tools to automate creating terraform configuration and prepopulate state from existing resources, like terraforming, terraformer or cf-terraforming. But it is still cumbersome and laborious and in my experience, it's usually way easier to just recreate everything within terraform from scratch wherever that's possible.

🧪 Terraforming export existing AWS resources to Terraform style (tf, tfstate).

but it seems it's not like copilot, everything is specifically implemented for each lanuage... eg:https://github.com/aws/aws-toolkit-vscode/tree/master/src/codewhisperer/util/dependencyGraph you can see, each supported lang has it's own way to look for dependency.. so every generated code is context specific... not like in the case of copilot where everything is handled by one giant model....

something like this? https://github.com/aws/aws-toolkit-vscode/issues/941

🧰 AWS Toolkit for Visual Studio Code is an extension for working with AWS services such as AWS Lambda.