How Can I Avoid Surprise AWS Costs from Forgotten Resources?

Great question about your tool versus CloudCustodian! From what I gather, CloudCustodian is awesome but pretty complex. I think your tool aims for simplicity and quick results without all the YAML setup. It’s less about a full compliance tool and more about finding those orphaned resources quickly and easily. Perfect for folks who just want a straightforward look at their potential waste!

You might want to add a requirements.txt file with boto3; I think it’s missing right now.

I took a look at your tool, and I have some feedback for you. First off, it seems like there are no tests to guarantee that it works as intended, which can be a deal-breaker for me. Also, I noticed that you’re committing directly to the master branch; for a project like this, it would be more reassuring to see commits going through a more structured process. I'd recommend implementing versioning and documenting each change to give it a more professional feel. Security is another concern; I'd want to know exactly what permissions are needed, maybe even suggesting an example IAM policy in your documentation. All in all, it looks promising, but I think there are a few key elements that need addressing before I’d feel comfortable using it.