Q: How would you identify unused or over-provisioned cloud resources?
Actionable audit runbook for discovering and terminating ghost cloud resources: unattached EBS volumes, orphan managed disks, idle load balancers, unassociated Elastic IPs, and obsolete snapshots.
Want to master this scenario in a live sandbox? The Linux Foundation's FinOps Certified Practitioner (FOCP) Program covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: In every production cloud account over 1 year old, 15 to 25% of the monthly spend consists of 'zombie' or orphaned resources left behind by deleted clusters, test VMs, or failed CI pipelines.
The Top 5 Orphaned Cloud Culprits
Where ghost money leaks every month:
- Unattached EBS Volumes / Azure Managed Disks: When an EC2/VM is deleted, attached persistent volumes often remain (status
availableor unattached), continuing to bill per GB-month. - Unassociated Elastic IPs / Public IPs: Cloud providers charge an hourly penalty fee for allocated public IPs that are NOT attached to a running instance.
- Idle Load Balancers (ALB/NLB): Abandoned load balancers with 0 healthy targets or 0 request count that bill base hourly fees (~$25+/mo each).
- Old Snapshots & AMIs: EBS snapshots from deleted instances retained for years without retention lifecycles.
- Orphaned NAT Gateways: Idle NAT Gateways left running in obsolete testing VPCs billing ~$35/mo base + data transfer.
Discovery Tools & Automated Auditing
How senior teams automate identification:
- AWS Compute Optimizer & Cost Explorer: Flags over-provisioned EC2/RDS instances and underutilized EBS volumes.
- Azure Advisor: Generates automated Cost recommendations for idle virtual network gateways, unused disks, and downsized VMs.
- KubeCost / OpenCost: In-cluster real-time allocation tool that breaks down Kubernetes spend by namespace, deployment, and orphaned persistent volumes.
- Cloud Custodian: Open-source policy engine running automated custodial crons to tag and auto-terminate unattached volumes older than 7 days.
Quick CLI Audit Commands
Run immediately to find leaks:
- AWS Unattached EBS:
aws ec2 describe-volumes --filters Name=status,Values=available --query 'Volumes[*].[VolumeId,Size,CreateTime]' --output table - AWS Unassociated IPs:
aws ec2 describe-addresses --query 'Addresses[?NetworkInterfaceId==null].[PublicIp,AllocationId]' --output table - Azure Unattached Disks:
az disk list --query '[?managedBy==null].[name,resourceGroup,diskSizeGb]' -o table
- Top leaks: Unattached EBS/managed disks, unassociated Elastic IPs, idle ALBs with 0 targets, and forgotten NAT Gateways.
- Discovery tools: AWS Cost Explorer / Compute Optimizer, Azure Advisor Cost blade, and KubeCost for in-cluster visibility.
- Fast CLI checks: 'aws ec2 describe-volumes --filters Name=status,Values=available' to instantly find orphan storage.
- Automated prevention: Cloud Custodian or Lambda janitor scripts to notify Slack and terminate unattached disks after 7 days.
- Enforce mandatory tagging ('Environment', 'Owner', 'Project') in Terraform so untagged rogue resources cannot be created.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Engineering bespoke in-house developer tools instead of adopting standardized platform Golden Paths when configuring Detecting Eliminating Unused Bespoke internal tools create long-term maintenance debt and fragmented workflows, whereas standardized Golden Paths accelerate delivery.
- Overlooking infrastructure cost visibility and FinOps allocation tagging across multi-tenant environments when configuring Detecting Eliminating Unused Without granular resource tagging, engineering organizations cannot attribute cloud infrastructure costs to specific teams or business units.
- Failing to define explicit Service Level Objectives (SLOs) and Error Budgets to balance feature velocity with reliability when configuring Detecting Eliminating Unused Without agreed SLOs, engineering and product teams lack an objective data-driven framework to prioritize technical debt over new features.
- Neglecting automated continuous drift detection between declarative configuration and deployed cloud state when configuring Detecting Eliminating Unused Unmanaged drift accumulates over time, causing future automated deployments to fail or overwrite emergency manual adjustments.