Docs Playbook
Compute Rightsizing Guide
Convert underutilization data into instance rightsizing actions.
Oversized compute is one of the fastest-growing waste sources in mature environments where workloads change over time.
Detection Signals
- Sustained CPU and memory far below provisioned capacity.
- High-cost instance families with low business-critical load.
- Repeated recommendations in scan history across cycles.
Execution Steps
- Collect 7/14/30-day utilization baseline for each workload.
- Define candidate target size and rollback plan.
- Apply change during a low-risk maintenance window.
- Verify performance and update policy thresholds.
Provider Differences
| Provider Group | Operational Notes |
|---|---|
| AWS | Rightsize EC2 families and EBS throughput combinations. |
| Azure | Rightsize VM SKU classes with workload tiers. |
| GCP | Adjust machine types and sustained-use sizing. |
| Linode/Vultr | Downsize overprovisioned compute plans. |
Share
Pass the cleanup path to the next reviewer
Send the same remediation steps to engineering, finance, or the owner who needs to sign off.
Next Step
Run a focused scan, validate owners, then export evidence for approval and execution.
Save your first $1,000 before the next billing cycle.