Skip to main content

Ripple - CUR Specification Change Log

A summary of AWS Cost and Usage Report (CUR) specification changes and how they impact Ripple.

Written by Yo Fukuda
Updated this week

Overview

This article summarises how Ripple responds when changes are made to the AWS Cost and Usage Report (CUR). Since CUR specifications are frequently updated, only changes that have an impact on Ripple's operations are described here.


What is the Cost and Usage Report (CUR)?

As described by AWS, the CUR is "the most comprehensive cost and usage data" available. It is a report that aggregates extensive and detailed data on AWS costs, which can be enabled through the AWS Console.

Because CUR consolidates a large amount of information, the file size can be significant, making it inefficient to use as a raw CSV file. The standard method is to deliver the report to an Amazon S3 bucket and process the data from there.

Key features of CUR include:

  • If configured at the management account level, it captures usage data for all accounts under the organization.

  • It can also be configured on a per-member account basis.

  • Granularity can be set to hourly or daily.

  • Costs are recorded in USD.

  • CSV output to S3 is delivered in separate files on a monthly basis.


CUR Specification Change:

Cost Category from "Refund" to "SppDiscount"

Before the Change

When under contract with AWS through the Solution Provider Program (SPP), discounts were applied and the discount amount was reflected in Ripple's Adjusting Entries as "Refund".

After the Change

  • Reflected in Adjusting Entries billing data

  • Cost category changed from "Refund" to "SppDiscount"

  • In addition to Solution Provider Program discounts, other AWS contract-based discounts such as "Enterprise Discount" and "Private Rate Discount" are now classified in detail

  • These discount items are recorded in the recalculated billing data on a per-AWS-account basis

Impact on Ripple Usage Fees

Previously, when discounts were applied directly to usage fees as "Discount," the discount amount was not separately visible. After the change, discount amounts are aggregated and reflected separately in the recalculated billing data.

Example: For a special AWS contract where the list price is $100 and the discount is $20:

Ripple Billing Statement

Discount in Recalculated Data

Before the change

$80 (discounted amount displayed directly)

Not separately visible

After the change

$100 (pre-discount amount displayed)

$20 reflected under "Discount" category with a descriptive note


Need More Help?

If any errors occur during the process or if you have any questions, please reach out to us:

Did this answer your question?