Phase 6 Delete: Create differentiated backups per resource type before deletion. This runbook implements the forced backup strategy from phase-6-delete.md section 4: - Pre-backup validation (resource exists, isolation intact, cloud API accessible) - Backup strategy dispatch (10+ resource types x environments) - Backup creation with 3-retry + exponential backoff - Backup verification (metadata validation, restore hints) - Backup protection (tagging, lifecycle rules) - Escalation to manual if all retries fail - Report generation per resource
Final phase of the zombie resource cleanup workflow. Presents all Phase 2 findings (deep scan + observation) to the user for final human decision, executes confirmed deletions, and delivers a cost savings report.
Phase 2 Deep Scanner — performs deep technical and business scanning on candidate machines approved by the user. One agent per machine, max 8 concurrent. Agent uses whatever tools available (SSH/cloud APIs).
Executes batch isolation operations per Phase 3 plan, monitors observation period with 3-dimensional anomaly attribution, triggers auto-rollback on P0/P1 anomalies, and generates structured observation reports (passed/failed/uncertain). Implements "Proof by Silence" principle: if nothing breaks during observation, resource is confirmed as zombie and advances to deletion phase.
Generates human-executable isolation plans for zombie resources identified in Phase 1/2. Creates per-resource isolation strategies with pre-checklists, rollback procedures, and observation configurations, plus a global batch plan sorted by dependency safety. Never auto-executes isolation; all decisions remain with humans.
Phase 1 Suspect: Discover cloud resources and apply idle detection signals to identify zombie candidates. Prefer cloud monitoring API (CloudWatch/Prometheus/Datadog) for historical metrics. SSH fallback: see prompts/signals-compute.md for in-VM collection rules.
Cloud infrastructure cost optimization lifecycle -- identifies idle and underutilized resources, orchestrates safe isolation and observation, and manages the approve-decommission workflow to reduce cloud spend. Trigger phrases: "cost optimization", "infra cost", "zombie resources", "idle resources", "reduce cloud cost", "cloud waste".
Phase 6 Delete - Zombie resource deletion execution. Orchestrates a 6-step deletion process: pre-flight re-evaluation -> verify backup-creator backups -> deletion execution -> deletion verification -> metadata update -> audit + cost report. Supports batch deletion (10 per batch, 5-minute intervals), cascading cleanup across resource types, special elastic IP DNS check, complete audit trail and cost savings analysis. Backups are performed upfront by zombie-backup-creator; resource-cleaner only verifies that backups exist.