Support phone number change!

585-397-3200

The previous number will not work after December 31, 2023; please update your records accordingly. 

NEW: Transaction Type Filter

We’ve added a new filter called Transaction Type to advanced grouping that will surface more granular detail to better understand AWS Savings Plan and RI purchases and how they have been applied to the account. 

Using the Transaction Type filter, you will also be able to see savings plan negation rows separate from other credits or program (EDP, SPP, etc.) discounts. 

Note: Any billing data finalized prior to November 2023 will require a reload to make Transaction Type data available for filtering. The transaction types include: 

• BundledDiscount
• EdpDiscount
• Credit
• DiscountedUsage
• Fee
• Refund
• RIFee
• SavingsPlanCoveredUsage
• SavingsPlanNegation
• SavingsPlanRecurringFee
• SavingsPlanUpfrontFee
• Tax
• Usage

Please Note: Line item details - Data exports will detail each line item in detail. 

The Transaction Type filter replaces the previous “Exclude Credits” checkbox excluding both Savings Plan Negations and other credits, without an easy way to filter them separately.  

If you currently have any saved reports that utilized the “Exclude Credits” option, you will see that the Transaction Type filter is now automatically applied to mirror the effect that “Exclude Credits” had provided by not omitting Credit, EdpDiscount, Refund, or SavingsPlanNegations on the report.  

For Saved Filter use cases, existing Saved Filters will continue to work as intended. Any customer who has a Saved Filter using the Exclude Credit checkbox will have the Saved Filter converted to select the correct Transaction Types included in the Exclude Credits checkbox, as shown above. If you change the billing filter, backward compatibility is maintained. 

NEW: Savings Plan Unsharing for AWS

CloudCheckr customers may wish to retain the benefit of Savings Plans rather than share those benefits with their end customer. AWS writes actual consumption to the CUR file, which is ingested into CloudCheckr. When CloudCheckr customers prepare end-customer pricing for invoicing or showback/chargeback, they can configure Custom Costs and determine how the Savings Plan benefit should be allocated, as shown in the below screen capture. 

Savings Plan Unsharing is configured via Billing > Configure > Configure Custom Cost > Cost Allocation | Savings Plan Cost Allocation, and provides the capability to 'unshare' and remove the Savings Plan benefit from the consuming accounts that are not the purchaser of the savings plan, or within the account family of the purchaser. 

Savings Plan Unsharing is provided in addition to the existing two options (Use what is in the CUR, and Savings Plan Deallocation), and may be configured either for all AWS accounts or for selected Account Families. 

Unshare SPs for all AWS Accounts
Savings Plan Discounts (negations) line items are removed from the consuming accounts that are not the purchaser of the savings plan, or within the account family of the purchaser.

Unshare SPs for selected Account Families
Savings Plan Discounts (negations) line items for the selected account families are removed from the consuming accounts that are not the purchaser of the savings plan, or within the account family of the purchaser.

CloudCheckr’s Savings Plan Unsharing mimics AWS' deactivate Savings Plans discount sharing, allowing CloudCheckr customers to easily and reliably define how they wish to manage Savings Plan benefits.   

Savings Plan Unsharing may be used in combination with (or separately from) CloudCheckr’s RI Unsharing capability in use by many customers. 

Bug Fixes

• Resolved an issue where AwsWellArchitectedInvalidPermissions was displaying incorrectly when utilizing CloudCheckr’s WARA (Well-Architected Readiness Advisor).
• Addressed an issue where the Delete Azure Saved Filter API call was failing.
• Fixed an issue where changing currency in a scheduled invoice generator would force rounding to the second digit. 
• Resolved an edge case column header alignment issue in an advanced grouping csv export related to marketplace charges.
• Fixed an issue where when the L1 locked and the L2 didn’t automatically reprocess.