This content was provided as a Professional Contribution through the FinOps Certified Professional program.
Strategic AWS Cloud Commitment Management in the FinOps Framework
Summary: AWS Savings Plans management requires balancing the high discounts of long-term commitments with the agility needed for shifting business workloads. Practitioners recommend a “60/40 strategy,” allocating 60% of baseline steady-state consumption to 3-year commitments while reserving 40% for 1-year terms to hedge against uncertain usage. To mitigate both under- and over-commitment risks, teams can implement a routine of purchasing smaller, monthly 1-year SPs that incrementally track alongside actual usage growth. By requiring 12 months of historical data and establishing clear governance thresholds, organizations can confidently capture substantial rate optimizations without locking themselves into wasted capacity.
The FinOps Framework emphasizes three core principles: enabling teams to make informed trade-offs between speed, cost, and quality; fostering collaboration across finance, technology, and business teams; and taking advantage of the variable cost model of cloud. Commitment-based discounting sits at the intersection of the three principles, requiring careful analysis, cross-functional alignment, and strategic decision-making.
Our Cloud Infrastructure is on AWS and this paper focuses on terms and criteria specific to AWS.
What Are AWS Savings Plans?
Savings Plans (SPs) are a flexible pricing model in AWS that offers lower prices compared to On-Demand pricing in exchange for a specific usage commitment measured in dollars per hour for a one or three-year period.
By committing to spend a certain amount per hour (for example, $10/hour) at discounted rates, AWS automatically applies this commitment to eligible usage up to this commitment amount, with any usage beyond that charged at standard On-Demand rates. The discount is applied automatically across the cloud usage within the plan’s scope.
Types of Savings Plans:
- Compute Savings Plans: The most flexible option, providing up to 66% savings and automatically applying to Amazon EC2, AWS Lambda, and AWS Fargate usage regardless of instance configuration or region
- EC2 Instance Savings Plans: Offer higher discounts (up to 72%) but apply only to specific instance families within a chosen region
- SageMaker Savings Plans: Apply specifically to machine learning workloads on Amazon SageMaker
Payment Options:
- Payable All Upfront (highest discount)
- Partial Upfront (at least 50% upfront with monthly payments for the remainder)
- No Upfront (monthly payments with lower discounts)
Who Makes or Informs AWS Savings Plans Purchases?
FinOps Practitioners and Cloud Financial Analysts who are responsible for optimizing cloud costs and managing commitment-based discount programs. If you’re tasked with purchasing Savings Plans, this paper provides a strategic framework for balancing savings with flexibility.
Finance and Procurement Professionals who manage cloud budgets and need to understand the financial implications of multi-year commitments. The paper explains the risk/reward in language accessible to non-technical stakeholders.
Engineering and Platform Leaders who forecast infrastructure needs and must collaborate with finance teams on commitment decisions. Understanding this framework helps bridge the gap between technical capacity planning and financial optimization.
Cloud Architects and Infrastructure Managers who design cloud environments and can influence consumption. The workload decisions directly impact the effectiveness of commitment strategies.
Executive Stakeholders who approve significant financial commitments and need to understand how the organization balances cost optimization with business agility.
What This Guidance Doesn’t Cover
- Specific technical implementation details for individual cloud providers (AWS vs. Azure vs. GCP)
- Reserved Instances for specific services with different characteristics to compute Savings Plans
- Kubernetes-specific commitment strategies or containerized workload optimization
- Spot instances or other non-committed discount mechanisms
- Cloud cost allocation and chargeback methodologies (though these are prerequisites)
- Rightsizing and optimization strategies that should precede commitment decisions
- Multi-cloud commitment or provider-switching strategies
Prerequisites
Before implementing the strategy in this paper, organizations should have:
- At least 12 months of historical cloud usage data
- Basic cost allocation through tagging or labelling
- Visibility into which workloads are stable vs. experimental
- Cross-functional communication between finance and engineering teams
- Authority and process for making financial commitments
- Tools and/or processes for monitoring Savings Plan utilization
If these prerequisites aren’t in place, the focus must shift to “Crawl” phase described in the FinOps Maturity section.
The 60/40 Commitment Strategy
The 60% (3-year) / 40% (1-year) split represents a balanced approach that optimizes for both cost efficiency and flexibility. Using a 60/40 ratio (between 3-year and 1-year commitment length) addresses maximizing cost savings through long-term commitments while maintaining flexibility to adapt to changing business needs, by implementing monthly purchases of 1-year Savings Plan as a risk mitigation mechanism. This helps reducing both under-commitment and over-commitment risks.
3-Year Commitments (60%): These address the predictable, steady-state portion of cloud consumption. By committing most of the baseline usage to 3-year terms, organizations capture maximum discount rates. This portion covers workloads with high confidence of long-term stability, such as core production systems, established applications, and infrastructure supporting fundamental business operations.
1-Year Commitments (40%): This portion provides a hedge against uncertainty. One-year terms offer meaningful discounts while allowing for annual reassessment of commitment levels. This flexibility is valuable for organizations experiencing growth, undergoing digital transformation, or operating in dynamic market conditions where technology decisions may shift more rapidly.
Risk Mitigation through Monthly 1-year Savings Plans Purchases
The Under-Commitment Problem: Under-commitment occurs when actual usage exceeds purchased commitments, forcing organizations to pay higher on-demand rates for the overflow. This is particularly costly because the delta between committed and on-demand pricing can be 50-70%. Organizations experiencing growth, launching/developing new products, or underestimating baseline consumption face this risk.
The Over-Commitment Problem: Over-commitment means purchasing capacity that goes unused, representing sunk costs that deliver no value. This typically occurs when business conditions change, applications are decommissioned, workloads are optimized more aggressively than anticipated, or initial forecasts prove overly optimistic.
The Monthly 1-year SP Purchase Strategy brings optimal solution to both problems.
Mechanism: Each month, the organization purchases a small Savings Plan for 12 months based on the previous month’s utilization patterns. These purchases accumulate over time, creating a portfolio of commitments that closely tracks actual usage growth.
Under-Commitment Risk: If usage grows 5% month-over-month, the next month’s 1-year SP purchase can reflect that growth. The commitment is small enough that the risk of waste is negligible.
Over-Commitment Risk: If usage declines, simply pause new 1-year SP purchases and allow existing commitments to expire naturally.
Implementation Framework
Month 1: Establish baseline with 60/40 split based on 6-12 months of historical usage data
Months 2-12: Purchase Quarterly 3-year SPs and monthly 1-year SPs targeting 85-90% coverage of existing usage
Quarterly: Review utilization metrics and adjust monthly purchase amounts if required
Annually: Reassess the core 60/40 commitment during 1-year SP renewal periods
FinOps Maturity and Commitment Strategy
The FinOps Framework describes three phases of maturity: Crawl, Walk, and Run. Commitment strategy should align with organizational maturity.
Crawl Maturity
Organizations should focus on visibility and basic optimization. Start conservatively with smaller commitments (e.g., 70% 1-year, 30% 3-year) and focus on understanding usage patterns. Monthly purchases are particularly valuable here as a low-risk approach.
Walk Maturity
Increase commitment levels as confidence grows. The 60/40 split becomes appropriate once the organization has 12+ months of usage data, established tagging and allocation practices, and cross-functional alignment on cloud strategy.
Run Maturity
Optimize the ratio based on sophisticated forecasting, consider portfolio optimization across multiple cloud providers, and implement advanced automation for commitment management. The monthly purchase mechanism becomes a fine-tuning tool rather than a primary risk mitigation strategy.
Governance and Decision-Making
Effective commitment management requires clear governance.
Decision Authority: Approval of commitments at different levels must be known in terms of DFA value limit required for big purchases (e.g., higher values require multiple Executive Leaders’ sign-off).
Metrics and Monitoring: Track coverage rates (target: 85-95%), coverage ratios (committed vs. total usage), and savings realization (actual savings vs. theoretical maximum).
Regular Reviews: Monthly operational reviews of utilization, quarterly strategic reviews of commitment mix, annual reassessment aligned with business planning cycles.
Cross-Functional Collaboration: Engineering provides technical forecasts and workload roadmaps, Finance manages budget allocation and risk tolerance, Product/Business contributes strategic direction and growth expectations.
Challenges and Considerations
Forecasting Accuracy
Cloud usage forecasting is difficult. Business plans change, optimization efforts exceed expectations, and new technologies alter consumption patterns. The 60/40 strategy acknowledges this uncertainty by limiting long-term commitments to the most stable portion of usage.
Multi-Cloud Complexity
Organizations using multiple cloud providers must manage commitment strategies across different platforms, each with unique discount structures and commitment options. The principles remain consistent, but implementation requires provider-specific optimization.
Technical Constraints
Not all workloads are eligible for Savings Plans. Specialized services, certain instance families, or specific configurations may require Reserved Instances or other commitment types, which are not the scope of this paper.
Conclusion
Commitment-based discounting represents one of the highest-value opportunities in cloud financial management, but it requires a thoughtful strategy that balances cost optimization with business flexibility. The 60/40 split between 3-year and 1-year Savings Plans provides a strong foundation, capturing significant savings while maintaining adaptability.
The monthly Savings Plan purchase mechanism is a powerful risk mitigation tool that addresses both under-commitment and over-commitment concerns. By making small, frequent adjustments based on actual usage patterns, organizations can continuously optimize their commitment portfolio without exposing themselves to significant financial risk.
Within the FinOps Framework, this approach reflects the core principle of enabling informed trade-offs. It acknowledges that perfect optimization is impossible — usage will fluctuate, forecasts will be imperfect, and business conditions will change.
Organizations implementing this strategy must start conservatively, establish clear governance, monitor performance metrics rigorously, and adjust the ratio over time as their FinOps maturity increases.
With discipline and cross-functional collaboration, this balanced approach to commitment management can deliver substantial cost savings while supporting the agility that makes cloud computing transformative.
Recommendations
- Start with Analysis: Review 12 months of usage history to establish a confident baseline before implementing the 60/40 split
- Implement Gradually: Begin with conservative commitments and use monthly purchases to build coverage incrementally
- Automate Where Possible: Use cloud provider tools or third-party platforms to monitor utilization and trigger purchase recommendations
- Establish Governance: Know decision levels and $ value limits, including escalation paths for commitment decisions
- Measure and Adjust: Track utilization rates, savings realization, and coverage ratios; refine the strategy quarterly based on performance
- Align Cross-Functionally: Ensure engineering, finance, and business stakeholders understand the strategy and their roles in its success
This commitment strategy is not a one-time decision but an ongoing practice that requires attention, analysis, and adaptation. When executed well, it transforms commitment-based discounting from a source of anxiety and risk into a competitive advantage in cloud financial management.
