What problem does it solve? Deciding which AWS EC2 instances, EBS volumes, AMIs, and snapshots are safe to delete is risky without evidence. This Skill produces a read-only, classified inventory across one or more AWS profiles/accounts so cleanup decisions are based on data, not guesswork, before any termination, deletion, or deregistration happens. ## Core Features & Use Cases - Read-only multi-account inventory: Collects EC2, EBS volume, AMI, and snapshot data per profile/region using AWS CLI describe calls, saving raw JSON evidence under a timestamped directory. - Safety classification: Sorts resources into buckets like cleanup-candidate, cleanup-after-scan, needs-owner-confirmation, and retain-protected, checking TTLs, SSM pointers, launch templates, AMI-to-snapshot mappings, and sharing permissions. - Structured RESULT.md output: Produces DEV/PROD-separated review tables with cleanup candidates first, confidence and reasons, rough cost notes, and the exact approvals needed. - Use Case: Before retiring expired AMI Factory validation resources, run this Skill to list which DEV and PROD EC2s, volumes, AMIs, and snapshots are cleanup candidates versus protected, then hand the approved list to terraform-terragrunt-cleanup or the owning repo command. ## Quick Start Ask the agent to build a read-only cleanup inventory of EC2 instances, EBS volumes, AMIs, and snapshots across your DEV and PROD AWS profiles and show the cleanup candidate tables.
