Unused-resource scans run CloudBurn's discovery rules against a connected AWS account and surface resources that are costing money without doing work — unattached volumes, idle load balancers, stopped instances still billing for storage, and the rest of the discovery rule catalog. Results stay in your own S3 results bucket; CloudBurn reads them to render your dashboard but the data lives in your account.
Prerequisites
- A connected AWS account with role, storage, and Resource Explorer verified
- A plan with dashboard access — see Plans and billing
Reading the results
Findings are grouped by rule. Each group shows the rule ID, name, and description — the same CLDBRN-AWS-* rules the open-source toolkit runs, so the Rules documentation is the reference for what each finding means, why it matters, and how to remediate it.
Each finding also carries a remediation effort badge (low, medium, or high) so you can triage: a low-effort finding like an unattached EBS volume is a five-minute win, while a high-effort one may need a migration plan.
Cloud scan vs. CLI discovery
The scan is the managed equivalent of running cloudburn discover yourself: same rules, same findings, but CloudBurn operates the scan through the read-only role instead of your local AWS credentials, and keeps history in your results bucket.
What's next
| Read this | To learn |
|---|---|
| Rules documentation | What every rule checks and how to remediate findings |
| Connect an AWS account | Add another account to scan |
| CLI discover command | The self-hosted equivalent of these scans |