Costfluent Docs
  • Pricing
  • Changelog
  • costfluent.com
  • Documentation
  • Guides
  • API Reference
Product
  • Pricing
  • Security
  • Changelog
Developers
  • API reference
  • Terraform
  • llms.txt
Legal
  • Privacy
  • Terms
  • Imprint
Get started
Concepts
Connect a source
Reporting
Allocation
Planning
Optimization
    InsightsSavingsCommitmentsKubernetes efficiency
Administration
Developers
Optimization

Commitments

Read how much of the usage your savings plans, reservations and committed use discounts can cover they do cover, what they saved against on-demand prices, and what you paid for and did not use.

Commitments sits under Optimization in the product's sidebar. It reads your cost data for the usage a commitment covered: an AWS Savings Plan or Reserved Instance, an Azure reservation or savings plan, or a Google Cloud committed use discount. It lists the AWS reservations and Savings Plans your connections hold, with their utilization and how soon each ends, and for the last three months it shows each provider's coverage figures over the whole window and month by month.

Before you start

  • Any team role can view the page. It is available on every plan.
  • The coverage figures come from the cost data Costfluent already collects. They need no extra permission on the connection.
  • Commitments held needs an AWS connection whose role may call ce:GetReservationUtilization and ce:GetSavingsPlansUtilizationDetails. Costfluent reads them once a day: six Cost Explorer calls per connection, which AWS bills at 0.01 USD each.

Commitments held

Commitments held lists each reservation and Savings Plan the workspace's AWS connections hold, for the accounts the workspace reads, the soonest end first. Each row shows its type, account, region and connection, its Utilization and Unused (30 days) cost over the last 30 days, and when it Ends:

  • The days left, when it ends within the next 30 days.
  • Expired once it has ended.
  • No end stated when AWS does not give one, which happens for some Savings Plans.

The list is read once a day. A connection whose role cannot read utilization keeps the last list it read.

When a commitment comes within 30 days of its end, every workspace that lists it gets one notification in the bell, which opens Commitments. Each commitment is announced once per term: a renewed one, with a new end, is announced again when that end draws near.

Read your commitment figures

  1. Open Commitments under Optimization.
  2. Read Last three months by provider for each provider's figures over the window.
  3. Read By month for the same figures one month at a time.

Each row shows:

  • Coverage: the on-demand value of the usage a commitment covered, over the on-demand value of all usage of the services a commitment covered.
  • Effective savings rate: how much less that usage cost, with unused commitment and commitment fees, than its on-demand value.
  • Unused commitment: what you paid for and did not use, at amortized cost.
  • Covered (on-demand) and Eligible (on-demand): the two values coverage divides.

To break the same usage down further, group or filter a cost report by Commitment status, Commitment type or Pricing category (Explore costs).

How it behaves

  • A service counts as eligible when a commitment covered any of its usage in the window. Usage of a service no commitment covered does not lower coverage.
  • The figures are always at amortized cost, whatever the report settings say.
  • Azure reservations state no list price, so their amortized cost stands in for the on-demand value. Their savings rate reads lower than it was.

Google Cloud does not report unused commitment, and its commitment fees and the credits they buy do not add up to one. The Unused commitment column shows a dash for Google Cloud rather than a figure that would be wrong.

  • A workspace whose costs are billed in more than one currency shows no figures until currency conversion is on (Currency).
  • Commitments held lists AWS commitments only. Azure states reservation utilization only at billing-account scope, which a connection's subscription-scoped role cannot read, and Google Cloud commitments are not read.

Related

  • Explore costs
  • Savings
SavingsKubernetes efficiency
On this page
  • Before you start
  • Commitments held
  • Read your commitment figures
  • How it behaves
  • Related