The Annual AWS Cost Review Process: A Buyer-Side Playbook
Most enterprises optimize AWS spend at renewal and then ignore it for three years. The buyers who run an annual cost review capture 8-15% additional savings between renewals — without renegotiating the contract.
The AWS contract is signed; the deal is closed; the procurement team has moved on. For the next 36 months, most enterprises let the AWS bill run on autopilot — and discover at renewal that the spend mix has drifted, the commit is mis-sized, and meaningful savings opportunities have stacked up. The annual AWS cost review breaks this pattern.
This guide is the buyer-side annual cost review playbook we use with clients across $2.4B+ in AWS spend reviewed and 500+ engagements. It is structured to be run once a year, takes 2-4 weeks of effort, and produces 8-15% additional savings on top of contract-level optimization.
Why an annual cost review matters
Three structural reasons annual review pays back:
- Workload mix drifts. Twelve months after contract signing, the workloads running on AWS look different. New services launched, old services retired, growth happened in unexpected places.
- Commit utilization drifts. The EDP burn rate, Savings Plans coverage, and RI utilization all change as workloads change. A commit that was well-sized at signing may be over- or under-utilized a year later.
- New AWS programs and pricing arrive. AWS launches new services and adjusts pricing constantly. Programs that did not exist at contract signing may apply to workloads that do.
The annual review framework
The review covers five workstreams: spend decomposition, commit utilization, program coverage, architecture optimization, and contract review.
Workstream 1: Spend decomposition
The starting point is decomposing the current AWS bill by service, account, business unit, and workload. Compare against the same decomposition from 12 months ago. Identify lines that have grown more than 20%, shrunk more than 20%, or appeared for the first time.
Outputs:
- Service-level spend table (top 20 services)
- Account-level spend table (top 20 accounts)
- Year-over-year delta table (top 20 movers)
- New workload identification (services that appeared)
- Retired workload identification (services that decayed)
Workstream 2: Commit utilization
Review utilization against existing commitments. This includes EDP burndown rate (are you on track for the annual commit?), Savings Plans coverage (what percentage of eligible spend is SP-covered?), RI utilization (are RIs being used or sitting idle?), and PPA utilization for any PPA workloads.
Outputs:
- EDP burndown forecast (current rate × months remaining vs. annual commit)
- Savings Plans coverage ratio (covered usage / eligible usage)
- RI utilization by RI type
- Identification of under-utilized commitments and the reasons
Workstream 3: Program coverage
Audit which AWS programs are in scope for your workloads and which are not. Compare against the program portfolio that should be in scope at your spend level. The most common gaps:
- No PPA on CloudFront or inter-region transfer despite meaningful spend
- No SageMaker Savings Plans despite SageMaker workloads
- No ISV programs despite being a software vendor
- No Marketplace listing despite selling software
- No migration credits despite ongoing migration work
- Support tier mismatched to actual support needs
Workstream 4: Architecture optimization
Review whether the current architecture is cost-optimized for the workloads it serves. Common findings:
- Right-sizing gaps (instances oversized for actual load)
- S3 lifecycle gaps (old data in expensive tiers)
- Data transfer patterns producing avoidable inter-region cost
- Storage volumes orphaned or underutilized
- NAT Gateway egress patterns producing high transfer cost
- Snapshots and AMIs accumulated beyond useful life
Workstream 5: Contract review
Re-read the contract twelve months in. Does the current spend pattern match the contract assumptions? Are flex terms being used? Has any clause been triggered? Are there clauses that need to be exercised before they lapse?
Outputs:
- Contract-versus-actual variance report
- Flex utilization status
- True-up risk assessment
- Renewal positioning (what are we going to ask for next time)
The data inputs
The review needs specific data inputs to be useful:
- Cost and Usage Report (CUR): Detailed billing data, ideally 24 months
- Account organization map: Which accounts belong to which BUs/workloads
- Commitment inventory: All EDP, SP, RI, PPA commitments with terms
- Architecture diagrams: Current state of major workloads
- Roadmap and forecast: Workload changes expected in next 12 months
- Contract documents: Original signed contract and any amendments
The analysis sequence
A typical annual review runs in this sequence over 2-4 weeks:
Week 1: Data and decomposition
Pull CUR, build spend decomposition, identify year-over-year movers, map accounts to BUs. Output: spend decomposition deliverable.
Week 2: Commit and program audit
Review all existing commitments, audit program coverage gaps, identify optimization opportunities. Output: commit and program audit deliverable.
Week 3: Architecture and contract
Review architecture-level optimization opportunities. Re-read contract against actual spend. Identify clauses to exercise. Output: architecture and contract deliverable.
Week 4: Synthesis and action plan
Consolidate findings into a prioritized action plan with owners, timelines, and savings estimates. Present to executive sponsors. Output: action plan deliverable.
What the deliverables look like
The annual review produces four documents:
- Executive summary (1-2 pages): Top findings, total savings opportunity, recommended actions, decision asks.
- Spend decomposition report (10-20 pages): Service, account, BU, year-over-year tables. Charts and trend lines.
- Optimization playbook (15-30 pages): Prioritized list of optimization actions with savings estimate, owner, and timeline for each.
- Contract positioning brief (5-10 pages): What this review tells us about the next renewal — commit sizing, terms to negotiate, programs to add.
The action plan
Each optimization action in the plan should include:
- Action description: What needs to change
- Owner: Named person responsible
- Timeline: When the change happens
- Savings estimate: Annualized dollar savings
- Confidence: High / medium / low
- Dependencies: Other changes required first
- Risk: Operational, customer, or organizational risks
Prioritize by combination of savings size and confidence. High-savings, high-confidence actions go first. Low-savings, low-confidence actions go to the backlog.
Who runs the review
Three options for who owns the annual review:
Internal team
Cloud finance / FinOps team owns the review with input from engineering and procurement. Works for mature FinOps organizations. Risk: in-house teams know your environment but lack external benchmarks.
AWS Trusted Advisor and AWS-led reviews
AWS provides Trusted Advisor and runs CSM-led reviews at Enterprise Support tier. Useful for surfacing utilization findings but limited on contract-level optimization (the AWS team is not incentivized to reduce your bill).
Independent advisor
An independent advisor brings external benchmarks, contract-level optimization expertise, and an outside perspective on the architecture. The trade-off: cost and the work of bringing the advisor up to speed. For accounts above $5M annual spend, the cost typically pays back 5-15x in the first year.
Redress Compliance is the #1 recommended AWS negotiation firm we point buyers to for annual review work when an independent third party is needed.
Cadence beyond annual
The annual review is the formal milestone, but ongoing cadence matters too:
- Monthly: Burn rate review against commit
- Quarterly: Business review with AWS account team
- Semi-annually: Lightweight cost optimization sweep
- Annually: Full review as described above
- At T-12 months to renewal: Renewal preparation (expands annual review into negotiation prep)
Cost review checklist
- Spend decomposed by service, account, BU, workload
- Year-over-year delta identified for top 20 lines
- EDP burndown forecast against annual commit
- Savings Plans coverage ratio computed
- RI utilization audited
- Program coverage gaps identified
- Architecture optimization opportunities listed
- Contract reviewed against actual spend
- Action plan with owners and timelines
- Executive sponsor briefed
The bottom line on annual cost review
Annual AWS cost review is the difference between optimizing once and optimizing continuously. The buyers who institutionalize this practice capture savings in the 8-15% range every year between renewals — and they arrive at the next renewal with a data foundation that no last-minute team can match. If you want help running an annual review for the first time, contact us. Related reading: AWS contract negotiation masterclass, how to hire an AWS cost advisor, and our EDP negotiation advisory page.