Cloud cost
Amortized, blended, and unblended cost
Three different bases for reporting the same underlying spend: unblended is the raw per-resource rate, blended averages a rate across an account, and amortized spreads upfront commitment costs evenly across the term they cover.
Last updated
Definition
Unblended cost is the simplest: the actual rate charged for each individual resource, with no averaging. Blended cost averages a rate across all usage of a resource type within a consolidated billing family. That's useful for a single effective per-unit rate across accounts, but it can mask which specific account or team is driving spend.
Amortized cost solves a different problem: a one-time or upfront commitment payment (buying a reserved instance for cash upfront, say) gets spread evenly across every day of the term it covers, so a single normalized daily number reflects the discount's ongoing value instead of showing one enormous spike on the purchase date and zero afterward. Most cost-monitoring tools default to amortized because it's the view that matches how the discount pays off over time.
Where it shows up
All three cost bases live in the same billing export: AWS's Cost and Usage Report carries an UnblendedCost column and a BlendedCost column side by side, and Cost Explorer's amortized toggle spreads an upfront commitment payment evenly across the months it covers instead of showing it on the purchase date.
What makes it expensive
The costly mistake is comparing a blended figure from a consolidated billing family against another account's unblended number and assuming they measure the same thing. Two dashboards will then quote two different totals for the same month, and both of them are right. Before reconciling anything, establish which cost basis each one is built on.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
A total nobody owns, nobody fixes.
An unattributed cost stays unowned. CostMon assigns spend to an owner, so someone can act on it.