Cloud cost
Idle and orphaned resources
Resources still running (and billing) despite doing no meaningful work: idle resources are underused, orphaned resources have no owner or purpose left at all.
Last updated
Definition
An idle resource is running well below any reasonable utilization threshold: a NAT gateway or load balancer left up after a migration, a staging environment nobody tore down. An orphaned resource has gone a step further. The thing it existed to support (an instance, a deployment, a project) is already gone, leaving a volume, snapshot, or elastic IP with no remaining reason to exist, still billing every month.
Both are the single most reliably reclaimable category of cloud waste, because unlike rightsizing there's no performance tradeoff to weigh. The only reason they persist is that nobody's looking; a recurring sweep against a normalized cost view is usually all it takes to find them.
Where it shows up
Idle and orphaned resources show up as line items with no corresponding activity: a NAT gateway or load balancer with near-zero traffic in its usage metrics, or a volume, snapshot, or elastic IP still billing on the invoice after the instance it supported was terminated.
What makes it expensive
Nothing in a cloud console announces that a resource has outlived its purpose. It just keeps running, and the assumption that anything still running must still be needed goes unchallenged for months. Only a deliberate sweep finds these. Walk the fleet against a normalized cost view and pull anything with no meaningful utilization or no parent left attached to it.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
The meter you don't watch still grows.
Waste rarely hides in the service you check every week. CostMon watches every meter on your stack, including the ones you forgot were running.