AWS
AWS Idle and Underused Resources
Review stale AWS infrastructure spend across unassociated Elastic IPs, idle load balancers, quiet databases, and the surrounding ownership drift that keeps old environments hanging around.
Detector Library
Find Hidden Cloud Cost Leaks Across AWS and GCP
Browse detectors for orphaned resources, leftover storage, idle infrastructure, and other cloud cost optimization opportunities hiding inside normal-looking services.
Use this library to uncover leftover storage, idle infrastructure, orphaned resources, and retention drift before those quiet cost leaks turn into recurring spend.
Why this matters
Common cloud cost leaks to review first
These are the recurring waste patterns that show up most often across AWS and GCP environments.
Leftover storage after teardown or migration
Detached disks, stale snapshots, incomplete uploads, and old object versions often keep billing after the workload that created them is already gone.
Browse storage-focused category guides →
Idle infrastructure that still charges every month
Public IPs and stale environments often survive because cleanup stopped halfway through or no owner closed the loop.
Review AWS infrastructure detectors →
Retention settings and billing choices that quietly raise spend
BigQuery billing models, bucket lifecycle rules, and log retention defaults can compound cost long after the original workload assumptions changed.
Review GCP data and storage detectors →
How to use this page
What you'll find in this library
The page is organized to get from a suspected waste pattern to the right next page without digging through a thin directory.
- Category guides for broader cleanup themes such as storage waste and stale-resource cleanup.
- AWS and GCP hub pages that narrow the library to the environment you are reviewing.
- Detector pages with the issue, likely cause, savings range, and remediation path.
Start here
Browse by category
Start with a common waste pattern, then drill into detectors that pinpoint the issue.
AWS CloudWatch Logs and S3
AWS Logging Cost Optimization
Reduce AWS logging cost by fixing missing retention and self-targeted access logging before quiet log storage turns into recurring waste.
AWS EBS and S3
AWS Storage Cost Optimization
Reduce AWS storage costs by finding detached EBS volumes and abandoned uploads after workloads are gone.
GCP
GCP Orphaned and Stale Resources
Uncover orphaned GCP infrastructure spend through unattached persistent disks and the ownership drift that leaves old environments partially retired.
GCP Cloud Storage and BigQuery
GCP Storage Cost Optimization
Reduce GCP storage costs by finding BigQuery billing model mismatches and GCS buckets whose lifecycle cleanup is still fully manual.
Detector search
Search every published detector
Filter by provider, cleanup area, or detector name when you already know the signal you want to validate.
Find a detector
Search by title, then narrow by provider or cleanup area.
No detectors match the current filters. Try a different provider, category, or search term.
FAQ
Is this page meant for quick wins or deeper optimization reviews?
Both. The detector library helps you spot obvious cleanup wins, but it is also meant to expose deeper cost misconfigurations that do not look urgent until they accumulate over time.
Why organize detectors by both provider and category?
Teams often approach cloud waste from two directions. Sometimes they know the platform they are auditing. Other times they know the waste pattern they are chasing. The library supports both entry points.
Do these pages replace manual cost review?
No. They sharpen it. The detector pages are intended to make manual reviews faster and more consistent by surfacing the hidden patterns that are easy to miss in ad hoc audits.
Early Access
Want these cost leaks monitored continuously?
Cloud Waste Hunter is being built to connect detector findings into one review flow with savings estimates, cleanup context, and practical next steps.