Cloud cost
Idle and orphaned resources
Resources that keep running and billing while they do no useful work. Idle resources are underused. Orphaned resources have lost their owner and purpose.
Last updated
Definition
An idle resource runs well below any reasonable utilization threshold. Examples are a NAT gateway or load balancer left up after a migration, or a staging environment nobody tore down. An orphaned resource has gone one step further. The thing it supported, such as an instance, a deployment, or a project, is gone. A volume, snapshot, or elastic IP remains with no reason to exist, and it still bills every month.
Both are among the most reliably reclaimable kinds of cloud waste. Unlike rightsizing, there is no performance trade-off to weigh. They persist because nobody looks. A recurring sweep against a normalized cost view is usually enough to find them.
Where it shows up
Idle and orphaned resources show up as line items with no matching activity. Examples are a NAT gateway or load balancer with near-zero traffic in its usage metrics. Others are a volume, snapshot, or elastic IP that still bills after the instance it supported was terminated.
What makes it expensive
A cloud console does not announce that a resource has outlived its purpose. It just keeps running. Nobody questions the idea that anything still running must still be needed, sometimes for months. Only a deliberate sweep finds these. Compare the fleet with a normalized cost view. Pull anything with no real utilization or no parent left.
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.