Improvements

• Added support for Azure EA agreements migrating to MCA within CloudCheckr Multi-Account Views (MAVs). 

Bug Fixes

• Addressed an issue with Licenses Charges for Azure PayGo subscriptions not being ingested.
• Solved an issue with the Azure Rightsizing Recommendation Report related to standard E-Series VMs.
• Fixed an issue with Best Practice Check “Ensure routing tables for VPC” which was providing duplicate data, and the link for “List of” was broken. 
• Fixed an issue where Charts in the RI Recommendations PDF Export were not matching (or were blank) the graphs in each result of the UI report. 
• Addressed a scenario where a negative custom charge value was created in its own service category, and was not reporting correctly in the single month summary report. 
• Resolved an issue with the Service Now integration not working properly in our High Security environment. 

Report Deprecation

• Cloud HSM reports have been deprecated. 

Release Notes 34.6

34.6 Improvements

• Added the option to provide a fallback fee assignment option within the Azure Reservation Configuration page (CMx UI: choose Billing/Configure/Reservation Billing Configuration)

  

• Clarified within the UI the specific ways that Uncompress Pricing Tier works 

34.6 Bug Fixes

• Addressed a Cost Saving Report issue (in Core UI only) would not display all results in a MAV  
• Fixed an issue preventing Azure Monthly Saved Filter emails for MAVs from being sent

Release Notes 34.5 - April 29th, 2024

34.5 Bug Fixes

• Fixed an issue preventing certain Trusted Advisor Checks from appearing 
• Resolved an issue where the Best Practice Check “Ensure routing tables for VPC peering are "least access"” check was incorrectly reporting with duplicates.
• Addressed an issue preventing programmatic invoice scheduling in AWS when using the API call “schedule_invoice” 

Improvements

• Support for Azure Israel Central region has been added
• It is now possible to edit each condition in Cost Allocator to update conditions as needed

Bug Fixes

• Resolved an issue where Last Login data was omitted from AWS List of Workspaces in the CSV export
• Addressed a scenario where Cost BI would fail to return data when filtering for “contains” using tag values if the volume of tags was very large 
• Fixed an issue where advanced grouping for Azure MCA did not reflect the Instance ID
• Addressed an issue where Cost BI $0 costs were included when “Include Zero Costs” was left unchecked
• The Manage Emails page in CMx now loads consistently 

Improvements

• Cost Allocator now supports the ability to match the exact ResourceID property. New options include “Match Key Exactly” and “Match Value Exactly.”

Bug Fixes

• Resolved an issue with the Azure edit_account_email_settings_v2 API call, which was returning an error code even when successful.
• Resolved an issue with the Azure create_subscription_family api was failing, incorrectly indicating the subscription is already assigned a subscription family – even though the subscription was not already in a subscription family. 
• Addressed a scenario where the Retail Cost for Azure Maps was not taking the free tier into consideration; feature request created with Microsoft to provide this information as part of their API response. 
• Resolved an issue where duplicate projects with the same AWS Account ID or Azure Subscription ID were incorrectly allowed to be created.
• Addressed an inconsistency between the EC2 RI Inventory vs EC2 Cost Summary when reporting the Total Instances Unused. 

Release Notes 34.2

Bug Fixes

• Fixed an inconsistency which caused a CSV export credential status to not match the UI status.
• Resolved an issue where Azure VM inventory was not populating correctly when license type UBUNTU_PRO and UBUNTU was used. 
• Resolved an issue where Savings Plan Analytics was reporting “There was a problem getting the Inventory data” and the section became blank.

Release Notes 34.0 and 34.1 - February 29th, 2024

Improvements

• Transaction Type filter is now available in the Custom Billing Charges Report.

Bug Fixes

• Resolved an issue where Savings Plan Analytics returned “There was a problem getting inventory data”. 
• Resolved an issue where “export users” CSV was failing.
• Addressed an issue where account level tags were not populating successfully.
• Resolved an issue where some Azure CSP spend was failing to ingest. 

NEW: Cost BI – Data Analysis Tool

We’ve added a new capability called Cost BI (Business Intelligence) to surface more granular detail regarding cost and usage within your cloud bill. In CMx, find Cost BI under the Cost menu.

With Cost BI, we have introduced a more robust solution to analyzing cost data. With this tool, users have more granular visibility on items (Accounts, Services, Descriptions, etc.) that can appear without needing to sort by a group by. Make changes in real time, move things around fluidly and dynamically, and see updates in real time. Users have the ability to load a dashboard and then drill into and analyze the details. 

Users can see multiple cost types side-by-side (IF user has access to multiple cost types), and quickly drill into your costs and the services that are generating them.  

NOTE: File Exports (csv format) are streamlined, omitting null data. Each item is now filled with relevant data in the Group-By, avoiding white space and simplifying downstream analysis you might conduct in Excel or other BI tools. 

Support Desk Update

CloudCheckr Technical Support is now using Zendesk as the primary ticket management system, helping us provide an improved support experience while also streamlining support across the Spot product portfolio, including Spot Security and the upcoming Billing Engine and Cost Intelligence products. 

Continue to contact our technical support team as usual:

1. Click on Contact Support from the Success Center
2. Send an email to support@cloudcheckr.com
3. Call our support directly at +1 (585) 397-3200, Monday – Friday, 8 AM to 9 PM Eastern Time
   (NOTE: this is a new phone number as of Jan 1st, 2024)

For those tickets created on January 22nd and beyond, CloudCheckr Technical Support responses will come from support@cloudcheckrspot.zendesk.com. Please be sure to add this email to your approved senders list.  All technical support tickets opened prior to January 22 will continue to be updated and managed in our legacy ticketing system (Jira Service Desk). 

Please send a message to support@cloudcheckr.com if you have any questions or feedback.

Improvements

• We have added the Transaction Type filter to the Custom Usage Rates report, allowing users to add boundaries based on transaction type that will impact certain rates. 
• We improved the EC2 cost summary report where we now show total unused reserved cost and unused reserve instance count that reflects more accurately the RI usage overview in an account.

Bug Fixes

• Addressed an issue with Azure cost ingestion being prevented, if on the previous run no new cost data was available. 
• Resolved an issue where the Azure Cost (Percent) alert did not display any tag keys when Filter By: Lookup tags is selected. 
• Addressed a scenario where customers could not create a new dashboard pane for Cost Monthly Summary type that included Azure Payees. 
• When using List Cost Analysis, we restored presenting the L2 RI unused hours line item. 

Support Desk Update

CloudCheckr Technical Support will begin using Zendesk as the primary ticket management system on January 22nd, 2024. The adoption of Zendesk will help us provide an improved technical support experience while also streamlining support across the Spot product portfolio, including Spot Security and the upcoming Billing Engine and Cost Intelligence products. 

All technical support tickets that were opened prior to January 22nd will continue to be updated and managed in our legacy ticketing system (Jira Service Desk). All new tickets created on or after January 22nd will be opened and managed in Zendesk. All users will continue to contact our technical support team as usual:

1. Click on Contact Support from the Success Center
2. Send an email to support@cloudcheckr.com
3. Call our support directly at +1 (585) 397-3200, Monday – Friday, 8 AM to 9 PM Eastern Time
   (NOTE: this is a new phone number as of Jan 1st, 2024)

For those tickets created on January 22nd and beyond, CloudCheckr Technical Support responses will come from support@cloudcheckrspot.zendesk.com. Please be sure to add this email to your approved senders list.

Please send a message to support@cloudcheckr.com if you have any questions or feedback.

Improvements

• Improved performance on both Billing Collector and Historic Collector cost ingestion jobs.

Bug Fixes

• Resolved an issue where the List of Reserved Instances (RI) report reported incorrect values in Total Instances Unused.
• Addressed an issue where Monthly Summary would sometimes redirect to account families page.

Support phone number change!

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

NEW: Copy CUR Functionality  

We’ve added a new ability to copy billing data from CloudCheckr to an S3 bucket in CUR format, in addition to the legacy DBR format. 

This report allows you to create a copy of the payer CUR, or subset of charges from your AWS Bill for a specific Payee including any adjustments specified in CloudCheckr, and copy that file into a selected S3 bucket.

The application will generate a new file based on the CloudCheckr Custom Cost (List) every time it ingests new data from the Payer’s AWS Bill of a given Billing Period, and copy that file into your selected S3 bucket.

To use Copy CUR, navigate to the Billing > Files > Copy Billing Data

The grid lists each of the Payees for the selected consolidated billing family. If you would like to publish the charges for a selected payee:

• Select a payee from the list
• Select a file format option
• Specify the S3 Bucket where you want the file to be copied
• Attach a bucket policy to your AWS credentials that allows you to read and write to the selected S3 Bucket

Improvements

• We’ve restored the legacy “Exclude Credits” checkbox in Advanced Grouping, now called “Exclude Charges less than $0” as this was the actual behavior. This legacy checkbox implies that Tax Refunds, reported by AWS as a negative value, are withheld from customers if the legacy “Exclude Credits” checkbox is selected.    

• Monthly Advanced Grouping Saved Filter emails can now be configured to be sent on a particular date of the month, and also to only be sent after a month finalizes, if desired. Navigate to Account Configuration at the top right of the screen and select Email Settings.

  

  
  

• This allows you to ensure that all Advanced Grouping Saved Filters that are configured to have an email report sent monthly will wait until a specific date or wait until the bill has been finalized if you have configured this to be a date after AWS might close their billing. If this is not configured you should expect to see saved filters emailed on the first of the month.
  
  

Bug Fixes

• Resolved an issue in Advanced Grouping where Tagged costs appear were being written to ‘none’ 
• Fixed an issue where CSV exports in cases where <$0.01 charges are being excluded from the CSV export were not matching the UI
• Resolved an edge case related to job timing where L2s were not reloading automatically after the L1 reloaded successfully
• Resolved an edge case where Azure billing ingestion was intermittently unsuccessful
• Savings Plan Analytics historical data is now populating correctly

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. 

Azure Subscription Family API

We have added new functionality to allow the creation, modification, and deletion of Azure Subscription Families APIs – see below for specifics regarding each API call: 

• Create: API Reference Guide 
• Modify: API Reference Guide 
• Delete: API Reference Guide 

Bug Fixes

• Addressed an issue where the payer closes a month as expected, and the payee was not being notified
• Addressed an issue where the high precision cost export was not being respected in some CSV exports
• Fixed an issue where – in certain scenarios – if autoscaling were used, the EC2 instance report was omitting some EC2 instances that should have been included 
• Resolved an edge case where the untagged resource report was incorrectly flagging a resource that had been tagged properly  
• Resolved an issue where tag values wouldn’t be visible in a MAV dashboard pane if multiple payers were selected
• Fixed an edge case where L2s were not receiving friendly names correctly