A city FinOps team reviews Cost and Usage Reports for sandbox OUs and finds Classic Load Balancers with zero traffic for months plus many unattached EBS volumes. Leadership wants a durable process to surface these waste patterns before renewing the next budget cycle. Which approach best identifies the unused resources from usage evidence?
Select an answer to reveal the explanation.
Short Explanation
CUR is the city’s meter tape—look for CLBs that never carried traffic and EBS volumes sitting unattached. Sandbox OUs are classic places this junk piles up. Use usage evidence, not gut feel, before you swing the cleanup axe.
Full Explanation
AWS Cost and Usage Reports (and Cost Explorer) expose resource- and usage-level dimensions that reveal idle Classic Load Balancers and unattached EBS volumes, especially in sandbox OUs. Architects should mine those reports for near-zero usage patterns and drive cleanup from evidence. Invoice PDFs alone lack granularity; deleting production balancers without metrics is reckless; consolidating NAT Gateways does not address idle CLB or orphaned volume waste.