steampipe-mod-aws-thrifty VS aws-nuke

2 - https://github.com/turbot/steampipe-mod-aws-thrifty

I feel your pain - but Steampipe won't solve this (yet). We have AWS Thrifty [1] to scan your env for cost savings and other tables to query your spend [2], but haven't tackled the 1.8GB of pricing JSON data into a table yet.

1 - https://hub.steampipe.io/mods/turbot/aws_thrifty

AWS Thrifty mod: includes over 40 cost saving controls to assess where you can optimize your spend on AWS: https://hub.steampipe.io/mods/turbot/aws_thrifty

I have scripted 25 checks for different cost savings/waste discovery opportunities on AWS based on issues I have seen in the past: https://github.com/turbot/steampipe-mod-aws-thrifty

To give this a slightly different spin:

--> "The best optimization is simply not spinning things up."

At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.

We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".

What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.

We use nuke aws at work to remove any leftovers: https://github.com/rebuy-de/aws-nuke

You can use this tool on github to nuke all resources.

There's this. I haven't used it myself, but it looks to be pretty effective: https://github.com/rebuy-de/aws-nuke

At this scale, operations can take a lot of time, because there are multiple operational tasks that we need to do when AWS accounts are leaving the AWS Organization or Teams are nuking the AWS account, StackSets Instances get drifted, because not all required resources for compliance can be secured ( SCP Limitations ), existing AWS accounts are joining the AWS Organization and all mandatory StackSets needs to be deployed, and manual steps should be reduced to a minimum. Furthermore, there is no feature from the Service itself to gain an overview of the status of drifted Instances and the general health of your StackSet health and compliance.

Since you're using CDK already, have a way to configure the deployment of the whole thing to a per-developer test account; that's still gonna cost you, but you can bundle everything in an organization / organizational unit for billing purposes, and you can also schedule https://github.com/rebuy-de/aws-nuke to run nightly to clean these accounts from longer-running resources.

And by extension, https://github.com/rebuy-de/aws-nuke as well.

I can also recommend aws-nuke which is an easy to way to destroy in your account.

nothing blew up accidentally this week, but our team at kubefirst is falling more and more in love with aws-nuke. it's an open source command line tool that lets you basically reset an aws account back to an empty state. if you have an environment where you regularly practice your platform provisioning, you probably know that failed destroys while iterating on orchestration can leave junk behind pretty easily. aws-nuke has been so nice to be able to blow away everything in an aws account - and then we just run terraform in the account to get all our core infra back afterward. nice allowlist filters and dryrun detail work too. check them out.