You don’t need a FinOps platform to find the first round of savings. You need an afternoon, read access to billing, and this list.
The nine checks
- Tags: what share of spend is tagged with an owner and an environment? Untagged spend is unowned spend.
- Idle resources: unattached volumes, unused IP addresses, old snapshots, load balancers with no targets.
- Non-production schedules: do development and test environments run nights and weekends?
- Rightsizing: instances and databases running well under their capacity for weeks.
- Commitments: steady workloads still paying on-demand prices instead of savings plans or reservations.
- Storage tiers: data that’s rarely read sitting in the most expensive tier, with no lifecycle rule.
- Data transfer: traffic between regions and zones, and egress to the internet. Often the surprise line.
- Logs and metrics: retention periods nobody chose, and debug logging left on.
- Budgets and alerts: is someone told when spend jumps, before the invoice arrives?
After the afternoon
Write each finding down with an owner and an estimate, fix the safe ones that week, and schedule a monthly 30-minute review. The habit matters more than the first cut.
Sources
- AWS Well-Architected: Cost Optimization Pillar (opens in a new tab)
- FinOps Foundation: FinOps Framework (opens in a new tab)
Last reviewed October 2026