0
The AWS Cleanup We Keep Putting Off (I Let an Agent Do It)
TL;DR: Aiming to cut AWS costs, the author delays cleanup until an agent helps. They cleaned old CloudFormation stacks, tackled a stubborn stack, and had the agent scan the entire account for remaining bill-generating resources.
Forgotten AWS resources quietly accumulate costs. The author used an agent to guide cleanup, deleting outdated CloudFormation stacks and overcoming a deletion failure in one stack. The agent then performed a full-account scan to identify leftover resources that were still running and driving bills. The result was a more comprehensive cleanup beyond manual queue-by-queue fixes.
Question for the room: What automation or agent-assisted cleanup steps have you found most effective for auditing and removing unused AWS resources?
— via dev.to
Add a comment
0/2000