Top 10 Recommendations for Negotiating AWS Savings Plans

Why this research paper exists

AWS Savings Plans replaced the legacy Reserved Instance model as the primary cost discount mechanism for AWS compute consumption. The structure is dollar denominated rather than capacity denominated. Customers commit to a flat hourly spend across compute services in exchange for a discount against on demand list rates. The structure is flexible and powerful, but it also creates a new category of buyer side risk. Unused Savings Plan commitments do not refund. The customer who commits at the AWS proposed coverage level often pays for compute capacity that no longer matches the production workload. The Savings Plan layer is the second most important commercial decision after the EDP itself.

The AWS account team approach to Savings Plan adoption follows three established patterns. First, the aggressive coverage pattern, in which AWS proposes ninety to ninety five percent coverage of projected compute consumption, often projecting twenty percent year over year growth that the customer has not committed to internally. Second, the three year all upfront pattern, in which the maximum discount is achieved at the cost of locking the largest cash outlay into a payment that captures no time value of money benefit. Third, the EC2 Instance Savings Plan default pattern, in which the higher discount on a specific instance family obscures the loss of flexibility across the broader EC2 portfolio. Each pattern carries distinct commercial implications. The customer who treats Savings Plan adoption as a simple discount discussion misses the leverage available in the coverage target, the term and payment option choice, and the workload classification.

We wrote this paper in May 2026, after the maturation of the Compute Savings Plan as the default coverage instrument, the stabilization of EC2 Instance Savings Plans inside high concentration workloads, the introduction of SageMaker Savings Plans for AI workloads, and the establishment of multi cloud workload portability as a standard enterprise posture. The recommendations are current. If you want the deeper procedural AWS RI and Savings Plan Optimization guide that pairs with this paper, the companion piece covers the operational mechanics. If you want the live advisory engagement that wraps both, the AWS buyer side advisory page describes the scope.