Here is the CLI you can run yourself <a href="https://github.com/gruntwork-io/cloud-nuke" rel="nofollow">https://github.com/gruntwork-io/cloud-nuke</a>
Open source CLI to do the same for free without passing AWS keys to third-party: <a href="https://github.com/rebuy-de/aws-nuke" rel="nofollow">https://github.com/rebuy-de/aws-nuke</a>
I launched Cloud Nuke to make it easy to safely delete AWS resources in 3 clicks!<p>I've found that deleting idle & underutilized cloud resources is the quickest win to reduce spending on cloud bills. Additionally the workflow of deleting cloud resources often exist in Engineering teams but it is not well thought out and a single member scrambles to determine what needs to be deleted.<p>Building on clouds is getting easier, and conversely harder to delete since resources often depend on each other.
It's a few years since I've used AWS, but is deleting stuff that hard? I seem to remember it was a matter of deleting a cloud formation stack and maybe cleaning up a few things that you'd explicitly ask to be preserved (usually storage things like S3 buckets and DBs).
> Q: Do you store my card?<p>> A: No payments are proessed directly by Stripe and we don't store your card details<p>"Let's eat grandma".
Thanks for all the feedback HN, I do agree the service is a risky tool so right now I've stubbed it out, effectively disabling its use while I figure out how to address the comments here