This article summarizes how Ripple responds when changes are made to the AWS Cost and Usage Report (hereafter, CUR). Since CUR specifications are frequently updated, please note that only changes that have an impact on Ripple’s operations are described here.
What is the Cost and Usage Report?
First, let’s briefly explain CUR. As AWS describes it as “the most comprehensive cost and usage data”, CUR is a report that aggregates extensive and detailed data on AWS costs. You can enable it through the AWS console, where a link to the actual configuration screen is provided on the CUR information page.
Because CUR consolidates a large amount of information, the file size can be heavy, making it inefficient to download and use as-is in a CSV file. The standard method is to deliver the report file to an Amazon Simple Storage Service (Amazon S3) bucket and then 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:
Change of Cost Category from “Refund” to “SppDiscount”
Ripple specification 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.”
Ripple specification after the change:
Reflected in Adjusting Entries billing data
Cost category changed from “Refund” to “SppDiscount”
In addition to discounts under the Solution Provider Program, other AWS contract-based discounts such as “Enterprise Discount,” “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 in the recalculated billing data.
Example:
For a special AWS contract where the list price is $100 and the discount is $20:
Before the change: The discounted $80 was directly displayed in Ripple’s billing statement.
After the change: The pre-discount $100 is displayed in Ripple’s billing statement, and the $20 discount is separately reflected in the recalculated billing data under the “Discount” category along with a descriptive note.