Show HN: Cloud-cost-CLI – Find cloud $$ waste in AWS, Azure and GCP(github.com)
4 pointsby vuhp5 days ago1 comment
  • preston-kwei4 days ago
    Historical tracking is useful, but only if it’s dead simple. If it requires standing up a DB or service, I probably won’t use it.

    I've been trying to track down cloud waste recently after realizing EC2 was storing 10GB snapshots every 12 hours for the past 8 months and I didn't realize. Obviously not a crazy 20k bill, but still annoying -- especially at small scale.

    • vuhp4 days ago
      Thanks! Actually I already built Option 1 (JSON files + compare command), just haven't published it yet. Will be in the next release.

      But your comment made me think about Option 2 more - exporting metrics to existing monitoring stacks, OTel/Prometheus. For teams already using them, that might actually be "dead simple" since there's no new tool setup or learn.

      I would appreciate any suggestions.

      • preston-kwei4 days ago
        I'm not sure how AWS logs work since I'm just used to looking at Cost Explorer... But I would assume they actually store the history themselves, and you can just pull it.
        • vuhp2 days ago
          Thanks for the suggestion. I will look into that.

          Btw, the previous version didn't detect EBS volumes attached to stopped instances. I just released new patch version for that.