search

iann0036 / former2

Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
https://former2.com
MIT License
2.23k stars 268 forks source link

Where do scan results get persisted? #257

Open BigDataDaddy opened 2 years ago

BigDataDaddy commented 2 years ago

I have several AWS accounts, but one really big one. The big one takes hours to scan the whole account before I use the generator to create CF/TF. I'm concerned that trying to use Former2 in one of my small accounts will wipe out the scan results from the big account, making it really had to use the tool across accounts.

Therefore I'd like to know where the scan results are persisted and can they be preserved when going between AWS accounts on the same host and browser?

Thx

iann0036 commented 2 years ago

Hi @BigDataDaddy,

Thanks for reaching out.

Unfortunately the scans are ephemeral in nature and aren't stored long term. If you're not already using it, the CLI will likely scan a little faster overall, and you can diff against multiple outputs over time.

I believe if you switch credentials it will technically preserve results for the same browser session however I wouldn't rely on this behaviour.

BigDataDaddy commented 2 years ago

How hard would it be to enhance Former2 to store scan results some place in AWS, like DynamoDB, SimpleDB, or even S3?

The goal here is to save the very long time that scanning takes. For reference, I started a scan last night over 17 wallclock hours ago and ticking that according to Chrome's Task Manager has so far consumed ~9.5 hrs of CPU time and has 3.4G of JavaScript memory. If the tool could somehow reload a past scan or at least bootstrap from a past scan and then only scan for deltas I'm hoping that a large part of that 17+ wallclock hours and ~9.5 CPU hrs could be saved so that the user could get to the generation functionality much quicker. It really would be a huge improvement of the user experience for large AWS accounts.