Standardized Cloud Optimization Playbooks
Use these operating playbooks when a team needs one repeatable method for compute, storage, network, database, and platform cleanup across a mixed provider estate.
Docs > Scan & Governance > Playbooks
Use this page when a finding needs a repeatable investigation and cleanup workflow instead of a one-off console check.
Search Playbooks and Docs
Tip: press / to focus search.
Search the whole siteOperating Flow
Find Waste
Start with compute, storage, and network findings that recur every week.
Prioritize Actions
Use one playbook per resource class so owners can act without rebuilding context.
Run Weekly
Keep the same review pattern for engineering, finance, and management handoff.
Compute Idle Resources
Find low-usage instances and remove persistent idle compute spend.
Compute Rightsizing
Convert utilization evidence into low-risk rightsizing actions.
Storage Orphan Disks and Volumes
Identify detached block volumes and clean safely with retention guardrails.
Snapshot Retention and Cleanup
Control snapshot and image sprawl with policy-based deletion windows.
Object Storage Unused Buckets
Detect empty or inactive object storage that adds cost and governance drag.
Object Lifecycle Governance
Fix lifecycle drift, orphan multipart uploads, and stale object versions.
Network Unused IP Addresses
Release unassociated public IP allocations and reduce network baseline spend.
Load Balancer and NAT Waste
Consolidate underused edge gateways and improve cost-to-traffic efficiency.
Orphan Connectivity Assets
Clean stale DNS, tunnels, interfaces, and route artifacts before incidents occur.
Database Idle and Overprovisioned
Reduce managed database waste while preserving recovery and compliance requirements.
Platform Idle Services
Identify low-value app platform services that continue billing after usage fades.
What teams get from this structure
- One operating pattern that can be reused across providers instead of retraining every reviewer for every cloud.
- Provider differences stay inside the execution tables, where teams actually need them during review.
- Search, internal links, and related playbooks move readers toward action instead of page sprawl.
- Cleanup decisions become easier to hand from engineering to finance and management with the same terminology.
Use one operating pattern across providers, then hand off the same evidence pack every week.
Save your first $1,000 before the next billing cycle.