elC0mpa

I am not sure, but I think caveman is available for any model any agentic tool

Hello guys, I am just another backend/devops guy who works a lot with AWS doing mostly repetitive tasks. This is precisely the reason why I created aws-doctor, a CLI tool that allows you to audit your aws account, compare costs between current and last month for the same period and many other things

I already talked about this tool in this link (https://news.ycombinator.com/item?id=46675092) and today I just want to tell you about the recent major updates

1 - now you can generate the pdf reports from the terminal (no headless browser needed) from each flow: cost, trend, waste

2 - there are new checks added, like S3 buckets without lifecycle policies, idle rds instances and more..

3 - I built a dedicated docs site where you can quickly search for exactly what you need

The project also just crossed 400 on GitHub, which is a huge milestone for me! If you try it out and find it useful for your own infrastructure, I would really appreciate a star on the repo (https://github.com/elC0mpa/aws-doctor)

Thanks a lot for the detailed answer, will take a look at the examples

Wow, looks great. Just a quick general recommendations:

You should give a direct curl to an install.sh to provide a simpler installation step for you tool and besides I think it would be good to publish it on home brew for MacOS users.

This post came in a good moment because I am developing a CLI and I want to add some interactivity to it in the next major version and in some way your CLI has helped me with that.

This is my CLI (https://github.com/elC0mpa/aws-doctor)

There you can check how I implemented the home brew distribution and the install.sh file for the easy installation step

Don't know if you have any experience with golang or aws, but maybe it worth taking a look at aws-doctor (https://github.com/elC0mpa/aws-doctor). This is a CLI tool I built myself, in the future want to make it more interactive and I am looking for some CLI apps to take ideas from there

Well, maybe this is an unpopular opinion, but I prefer the Gemini Cli, I paid Google AI Pro for the year and it is perfect for me, even though it's true that pro model sometimes takes like 2 - 4 minutes to answer

hof looks pretty nice, definitely deserves a star, will also take a look at The Dagger. Thanks

Reaaly nice one tig, will definitely try it out. Thanks!!!!

Interesting POV

Thanks, anyways I have the Google AI Pro subscription for one year, so for now I will continue using Gemini

I forgot to add the GitHub repo:

https://github.com/elC0mpa/aws-doctor

I understand your position, however for some strange reason (maybe because like I am the kind of software engineer who liks to do most by himself) I haven't noticed any issue every time I ask Gemini to do something. Thanks anyways for your comment!!!

Project name: aws-doctor

Project description: Powerful open-source CLI to audit security, costs, and best practices in AWS.

What do you hope to build this month? Add new waste checks for the tool

What kind of skills do you need? AWS, Golang

I don't really think it is running to catch Claude, it's true that Claude is way better (for now) to developers, but Gemini in my opinion is a better tool. At least is what I use as a personal assistant. I have Claude because my job paid for it, but I pay Gemini CLI, it's true that sometimes when it uses Gemini Pro 3.1 model it stucks, but in general for me it is pretty well

I built aws-doctor because I found myself constantly repeating the same manual checks in the AWS Console to find wasted costs (orphaned EBS volumes, unattached IPs, old snapshots, etc.). I wanted a tool that could do a quick "health check" from the terminal without needing to export CSVs or click through the Cost Explorer UI.

The tool is written in Go and uses the AWS SDK v2.

I just launched this documentation site to make it easier to get started, but if you want to check out the code or the project structure, the repo is here: https://github.com/elC0mpa/aws-doctor

I'd love to hear your feedback on:

1 - What other "zombie" resources do you constantly find in your accounts? (I'm looking to add more checks).

2 - What new features you think might add value to the tool. I am thinking about exporting PDF reports

3 - Any feedback on the CLI design/UX.

Thanks!

Well, I really like building CLIs for my personal use, and I prefer Golang for both Backend and CLIs, I am currently working on aws-doctor (https://awsdoctor.compacompila.com/), An Open Source CLI to diagnose AWS costs, detect idle resources, and optimize cloud spending directly from your terminal. Let me know WDYT if you take a look at it.

Waooooo, I just look at Kvile and Stao and My Visual Routine. Great work!!! My favourite is Stao, definitely will try it, but before I need a standing desk. Keepo the hard work!

Wow, this looks interesting, great work!

Thanks a lot for your advice, I work every day with Terraform and I understand what you mean, but that is out of the scope at least right now, I want to keep this tool as simple as possible, but definitely this worth an analysis

Thanks!!! If you find something that can be improved, don't doubt opening an issue!

Sorry, I didn't understand the comment

Thanks, if you think about something that might be improved, please open an issue!!!

Hi HN,

I’m a Cloud Architect, and I built aws-doctor because I found myself constantly running the same manual checks across different AWS accounts to find "zombie" resources. While AWS Trusted Advisor exists, the best checks are often locked behind paid Business/Enterprise support plans, and the AWS Console can be slow when you just want a quick "health check."

What it does: It’s a TUI (Terminal User Interface) that acts as a proactive checkup for your account.

Waste Detection: Scans for stopped instances (>30 days), unattached EBS volumes, unassociated Elastic IPs, and expiring Reserved Instances.

Cost Diagnosis: Compares your current month-to-date costs against the exact same period last month (e.g., Jan 1–15 vs. Feb 1–15) to spot spending velocity issues.

Trends: Visualizes cost history over the last 6 months.

The Tech Stack:

Written in Go (1.24).

Uses AWS SDK v2.

UI built with Charm's Bubbletea and Lipgloss (for the tables/styling).

It’s completely open-source and runs locally on your machine (using your standard ~/.aws/credentials).

I’d love to hear your feedback on the code structure or suggestions for other "waste patterns" I should add to the detection logic.

Thanks!