An open-source, strictly read-only CLI tool that scans your AWS account in seconds to identify forgotten or oversized resources (EBS, EC2, NAT Gateways, RDS, and more). It generates instant expense reports (Table, JSON, MD, PDF) and integrates seamlessly into CI/CD pipelines. The project is evolving rapidly with exciting new features on the way! I'd love to know: what AWS resource or integration should cloudrift scan next? Drop your ideas below!
No reviews yetBe the first to leave a review for CloudRift
Maker
π
Hello Product Hunt community! πAnyone managing AWS infrastructure knows the drill: forgotten or oversized resources quietly burning budget, month after month. Often, the choice is either spending hours digging through the AWS Console manually or adopting complex enterprise platforms that require dedicated setups and budgets.To bridge this gap, I decided to automate the process in the leanest way possible and built cloudrift: an open-source CLI tool (Node/TypeScript) to instantly spot economic leaks.The idea is simple: a single command, an immediate report, zero friction.π What cloudrift currently analyzes:Compute & Database: Underutilized/stopped EC2 & RDS, idle clusters, and orphaned nodes.Storage & Backup: Unused EBS volumes, old unassociated snapshots, and unoptimized storage.Networking: Unassociated Elastic IPs, forgotten NAT Gateways, and idle Load Balancers (ALB/NLB/ELB).Serverless & Containers: Stale Lambda functions, inactive DynamoDB tables, and oversized ECS/EKS services.π‘οΈ "Zero-Friction" & Security First:Strictly Read-Only: The tool has zero write permissions. It works out of the box with the standard AWS ReadOnlyAccess policy.No Lock-in: No registration, no external databases, no dashboards to configure.Shareable Reports: Outputs directly to your terminal, but can also export to JSON, Markdown, or a team-ready PDF.Automation Ready: Designed to integrate into your CI/CD pipelines to fail a build if the estimated waste exceeds your custom budget threshold.It isn't built to replace large-scale enterprise FinOps giants. It's meant to be the quick, no-bullshit tool to instantly check the financial health of any sandbox or production account.I would love to get your feedback, critiques, and thoughts. What features or resource checks should I add next to make it indispensable in your daily workflow?Thanks for checking it out! π