Reading view

CleanCloud v1.6.3: scan feedback wanted (honest opinions welcome)

Posted here last week about CleanCloud - a read-only AWS/Azure hygiene scanner that runs in CI and flags orphaned, untagged, and inactive resources before they hit your bill.

Got around 200+ installs via pip, but zero feedback. Which means either:

a) It worked perfectly and nobody felt like commenting

b) Something broke and nobody felt like commenting

c) The findings weren't useful enough to care about

Genuinely don't know which one. That's why I'm asking directly.

If you installed it and ran a scan, what happened?

Even "it found nothing" is useful signal for me.

20 high-signal rules across AWS and Azure - each read-only, conservative, and designed to avoid false positives in IaC environments.

AWS:

  • Unattached EBS volumes (HIGH)
  • Old EBS snapshots
  • Infinite retention logs
  • Unattached Elastic IPs (HIGH)
  • Detached ENIs
  • Untagged resources
  • Old AMIs
  • Idle NAT Gateways
  • Idle RDS instances (HIGH)
  • Idle load balancers (HIGH)

Azure:

  • Unattached managed disks
  • Old snapshots
  • Unused public IPs (HIGH)
  • Empty load balancers (HIGH)
  • Empty App Gateways (HIGH)
  • Empty App Service Plans (HIGH)
  • Idle VNet Gateways
  • Stopped (not deallocated) VMs (HIGH)
  • Idle SQL databases (HIGH)
  • Untagged resources

Reader role only. Zero telemetry. Nothing leaves your subscription.

You can raise issues or create discussions in the repo below incase you think the engine is worth using it in the CI/CD pipelines or locally

https://github.com/cleancloud-io/cleancloud

pipx install cleancloud

cleancloud demo

cleancloud doctor --provider aws

cleancloud scan --provider aws

cleancloud doctor --provider azure

cleancloud scan --provider azure

What Aws/Azure waste checks would actually make you add this to your pipeline? That's what I'm building next.

Thanks

submitted by /u/Kind_Cauliflower_577 to r/devops
[link] [comments]
❌