Several micro AWS accounts for tiny city projects show idle Auto Scaling groups still billing. How should finance and architects improve accountability and cut waste?
Select an answer to reveal the explanation.
Short Explanation
Idle ASGs hiding in micro-accounts are like empty storefronts still paying rent. Tag the owners, look across consolidated billing, and shut down or merge the idle fleets.
Full Explanation
Requiring consistent cost-allocation tags, using consolidated billing views, and shutting down or consolidating underutilized idle Auto Scaling groups with clear owners is the correct accountability approach when several micro AWS accounts for tiny city projects still bill for idle ASGs. Tags and Organizations consolidated billing make waste visible across accounts; ownership then enables stop, scale-to-zero, or merge decisions. Removing all tags so Cost Explorer cannot attribute spend fails by destroying allocation visibility—the opposite of financial control. Creating a new untagged account for every idle ASG fails conceptually by spreading waste further and worsening attribution. Disabling Organizations to hide cross-account idle capacity fails as an anti-pattern that removes centralized visibility rather than eliminating idle fleets. Exam caveat: tag, consolidate visibility, and reclaim idle ASGs; do not remove tags, spawn untagged accounts, or disable Organizations to hide waste. Operational check: enforce mandatory cost tags via policy; review consolidated billing for ASG/EC2 idle patterns; assign owners; scale idle ASGs to zero or terminate; and schedule a monthly orphaned-ASG scrub across the city’s micro-accounts.