Savings Plan amortized cost converts a front-loaded or recurring Savings Plan fee into a daily rate you can actually reason about. The default unblended view shows what AWS billed your account each day so a 1-year All Upfront Savings Plan appears as a single large charge on Day 1, then silence for 364 days. Accurate for cash flow. Operationally useless for tracking commitment ROI, allocating costs to teams, or detecting underutilization.
Here's what amortized cost is technically, how it differs from unblended and blended, and critically how to use it to catch unused commitment before it compounds.
What Is Savings Plan Amortized Cost?
Amortized cost is a cost dataset in AWS Cost Explorer and the Cost and Usage Report (CUR) that spreads Savings Plan fees uniformly across each day of the commitment term. It's an accrual accounting view of your cloud spend.
The formula AWS applies:
Daily Amortized Fee = (Total Plan Fee) ÷ (Total Days in Term)
For a 1-year No Upfront Compute Savings Plan at $10/hour ($87,600/year):
- Daily amortized fee: $87,600 ÷ 365 = $240/day regardless of whether EC2 usage consumed 100% or 60% of coverage that day
For a 1-year All Upfront plan at $80,000:
Unblended view: $80,000 on Day 1, $0 for Days 2–365
Amortized view: $219.18/day every day of the term
The effective cost per covered compute-hour in the amortized view is the true discounted rate, the number finance should use for chargebacks, and the number you should monitor to verify your Savings Plan is performing as expected.
The key operational difference:
An unblended view tells you what happened to your AWS bill. An amortized view tells you whether your Savings Plan is working.
If usage drops 40% in Month 6 on an All Upfront plan, the unblended view gives you no signal the $80,000 is already spent. In the amortized view, Month 6 shows unused commitment cost as a daily line item. That's the waste signal.
If you want to understand how On-Demand, Reserved, and Spot pricing compares before committing, we covered the full breakdown here On-Demand vs Reserved vs Spot Instances: The Complete AWS Pricing Guide
How to View Amortized Cost in Cost Explorer
Prerequisites:
- Cost Explorer enabled (Billing → Cost Explorer → Enable)
- At least one active Savings Plan
- Permissions: ce:GetCostAndUsage, ce:DescribeSavingsPlans
Step 1: AWS Console → Billing and Cost Management → Cost Explorer
Step 2: Set a date range covering your Savings Plan's active period. 30 days minimum for utilization analysis.
Step 3: In the right-hand panel, open Advanced Options. The cost type defaults to Unblended.
Step 4: Select Amortized costs. If you have upfront Savings Plans, the previously lumpy daily cost line will flatten into a consistent daily rate.
Step 5: Group by dimension to see coverage distribution:
- Group by Service → EC2 vs. Lambda vs. Fargate coverage
- Group by Linked Account → which accounts received commitment coverage
- Filter: Purchase Option = Savings Plans → isolate commitment cost from on-demand
Step 6: In the amortized view, AWS surfaces two Savings Plan line items:
- Savings Plans recurring fee: daily amortized portion of the plan fee
- Savings Plans upfront fee: if All/Partial Upfront, also shown as a daily amortized value
When usage fully covers the commitment, these appear as negative offsets against on-demand charges, netting to the discounted rate. When usage doesn't cover the commitment, the unused portion appears as a positive cost with no offsetting savings. That's your waste.
What Unused Commitment Actually Looks Like
Assume a Compute Savings Plan committing to $5/hour ($43,800/year, 1-year No Upfront).
Daily Usage vs. Commitment Outcome
100% Full $5/hour applies, zero unused commitment
70% $3.50/hour applied, $1.50/hour unused = $36/day wasted
50% $2.50/hour unused, $60/day = $1,800/month for nothing
None of this is visible as a daily signal in the unblended view. In the amortized view, unused commitment appears as a real-time daily cost line.
At scale: A 30% underutilized Compute Savings Plan on a $500,000/year commitment generates $150,000/year in unused commitment spend that produces zero AWS resources. At $6–12K/day in potential waste for larger environments, a single underutilization event undetected for 30 days is a $180K–$360K problem.
If you're thinking through how to size and time your commitment purchases, we broke down the strategy here AWS Savings Plan Buying Strategy: Layering, Timing & Right-Sizing Commitment
Amortized Cost Across Consolidated Billing Accounts
In an AWS Organization, Savings Plans purchased in a management account can apply across all linked accounts. The amortized view is the only Cost Explorer dataset that properly attributes this coverage.
AWS applies the Savings Plan to usage across linked accounts (roughly by account ID, then by service). Each linked account's amortized cost reflects the discounted rate for covered usage, regardless of which account owns the plan. Unused commitment is allocated back to the plan-owning account.
Why this matters for chargebacks: The unblended view shows the purchasing account bearing the full Savings Plan cost. The amortized view distributes that cost to accounts that actually consumed coverage. For any accurate internal cost allocation, you must use amortized cost unblended will systematically overcharge the management account and undercharge linked accounts.
Sample Athena query to surface unused commitment by day:
SELECT
line_item_usage_start_date AS usage_date,
savings_plan_savings_plan_a_r_n AS plan_arn,
SUM(savings_plan_unused_commitment) AS daily_unused_commitment,
SUM(savings_plan_used_commitment) AS daily_used_commitment,
ROUND(
SUM(savings_plan_unused_commitment) /
NULLIF(SUM(savings_plan_used_commitment + savings_plan_unused_commitment), 0) * 100, 2
) AS unused_pct
FROM your_cur_table
WHERE line_item_line_item_type = 'SavingsPlanNegation'
OR line_item_line_item_type = 'SavingsPlanCoveredUsage'
OR line_item_line_item_type = 'SavingsPlanRecurringFee'
OR line_item_line_item_type = 'SavingsPlanUpfrontFee'
GROUP BY 1, 2
ORDER BY 1 DESC, 3 DESC;
Verify CUR field names against your specific CUR configuration field availability depends on CUR version and configuration.
The most common CUR mistake: summing lineItem/UnblendedCost and savingsPlan/SavingsPlanEffectiveCost in the same aggregation. That's double-counting. Choose one methodology and apply it consistently.
What the Amortized View Can't Tell You
Amortized cost is necessary for commitment analysis but not sufficient for commitment management.
Latency: Cost Explorer data has a 24–72 hour refresh latency. Savings Plans utilization can lag by up to 3 days. At $6–12K/day in potential waste, a 72-hour refresh cycle means a utilization problem can compound to $18K–$36K before it appears in your dashboard.
No forward-looking signal: The amortized view shows historical commitment performance. It can't tell you whether your current usage trajectory will overshoot or undershoot your commitment for the rest of the month.
No automated action: Cost Explorer shows you the problem of unused commitment as a daily cost line. Fixing it (adjusting commitment size, redistributing coverage, or recovering unused commitment value) requires a separate workflow.
Closing the Gap Between Signal and Action
Most teams review Savings Plans utilization monthly or quarterly. AWS Cost Explorer's recommendation engine refreshes every 72+ hours. By the time a utilization drop appears, gets reviewed in a weekly FinOps meeting, and reaches a decision, 2–4 weeks of unused commitment may have accumulated.
Usage.ai refreshes commitment data every 24 hours. On a $500K/year Savings Plan with 20% underutilization, you're burning ~$274/day in unused commitment and miss it for 3 days due to stale tooling, that's $822 gone before anyone sees the signal.
The other differentiator: most vendors in this space issue credits when commitment goes unused. Credits apply against future AWS invoices. Usage.ai returns cash actual money back, not a discount on next month's bill. Unused commitment stops being a sunk cost and becomes a recoverable one.
Setup operates at the billing layer with only no infrastructure changes, no access to production resources. Commitments are sized to actual baseline usage rather than peak, which directly reduces the unused commitment visible in your amortized cost view.
For FinOps teams managing a consolidated AWS Organization, the amortized view of unused Savings Plan commitment is the first diagnostic signal. The question is how fast you act on it.
How does your team currently monitor Savings Plan utilization Cost Explorer, CUR queries, a third-party tool, or something else?
For a deeper technical breakdown and additional insights, read the full article here → Understanding Savings Plan Amortized Cost in AWS Cost Explorer
Top comments (0)