reddit · SideProject · 10-12 20:50 55 分 ← 返回列表

NimbusWatch - I built a read-only AWS waste & security scanner without guessing on the math

I kept running into the same two small panics as a solo dev on AWS: unexpected cloud bills from forgotten test resources, and configuration gaps where I couldn't read an IAM policy with total confidence. Instead of dealing with generic cloud dashboards that either hide details or throw false positives, I built a tool to solve it for my own setup. Here is how it works under the hood. Why Read-Only by Architecture Matters The core design decision was making the permission model strictly

五维评分

付费意愿

需求真实度

个人可落地

竞争空间

新鲜度

AI 分析

痛点：独立开发者在 AWS 上因忘记清理测试资源导致账单意外超支，且难以自信地读懂 IAM 权限配置

目标用户：在 AWS 上自建部署的独立开发者、小型 SaaS 团队、DevOps/FinOps 工程师

证据：I kept running into the same two small panics as a solo dev on AWS: unexpected cloud bills from forgotten test resources, and configuration gaps where I couldn't read an IAM policy with total confidence.

变现：Freemium 订阅制 SaaS：免费只读扫描，按 AWS 账号数或扫描资源量分级收费，高级版提供持续监控、Slack/SES 告警与修复建议

MVP：用 ce:GetCostAndUsage 加一组只读 Get/List/Describe 权限，做闲置 EBS/EIP（14 天零活动）与低利用率实例（多日峰值 CPU）检测，输出 HTML/邮件报告并接 Slack 告警

竞品：AWS Cost Explorer、AWS Trusted Advisor、Vantage、nOps、CloudZero、Komiser、Prowler、Cloud Custodian

摘要：作者是独立开发者，因 AWS 账单意外超支和 IAM 权限难读这两个痛点，自建了只读架构的 NimbusWatch 扫描器。技术上用单一 ce:GetCostAndUsage 权限做成本追踪，安全与浪费扫描基于只读动作加写删除显式拒绝，闲置资源判定采用 14 天滚动零活动窗口以避免误报。帖中未提及定价、收入或付费用户，属于典型的产品发布，痛点真实但竞争已相当拥挤。