We were proud to announce initial support for AWS Savings Plans upon launch. Since then, the following reports have been updated with additional support as follows:
Savings from AWS Savings Plans will follow the EC2 Compute costs covered, enabling your chargeback and showback workflows just like Reserved Instances for one seamless experience. But wait there’s more… Savings Plan - Upfront charges and Savings Plan - Unused Fees are visible in the Cost History Report as their own unique line items and are available in Cost Reallocation. Essentially, you can now track and manage fees and how savings are applied by AWS Savings Plans in a similar manner you are used to from Reserved Instances.
Costs by Perspective Group - inclusive of Savings Plan fees and savings

Example view including new Cost History Report Dimensions

The EC2 Instance Cost & Usage Reports will fully support AWS Savings Plans and will include a new measure called “Coverage Type” that breaks down your EC2 cost or usage by:
EC2 Savings Plan
Compute Savings Plan
Standard RI
Convertible RI
On-Demand
Spot
The existing “Reservation Type” measure will now include AWS Savings Plans coverage in addition to Reserved Instance coverage (e.g. All Upfront will show All Upfront RIs and Savings Plans coverage). This unlocks new views such as Coverage Type by Instance Family, filtering existing reports by coverage type, and more.
Next week, we will be adding categorization, tagging, and inventory support for Savings Plans. CloudHealth will collect asset inventory data for Savings Plans every 15 minutes. Type, state and other details will be available in the Savings Plans Asset Report.
Reminder — Action Required: We require you to update your IAM policy for this service. Please add the following lines to your IAM policy:
savingsplans:DescribeSavingsPlans
For more details on how to do this, please visit our Help Center.
Learn more about CloudHealth’s support for AWS Savings Plans in this Help Center article. If you would like to discuss AWS Savings Plans with our Strategic Savings Desk team, please reach out to cht-savingsdesk@groups.vmware.com.
Last updated on November 21, 2019
As previously announced, we have developed a more comprehensive approach for extracting asset attributes from bills to allocate costs for AWS services using AWS and CloudHealth tags. Next week, we will be updating costs for the following services:
AWS Data Sync
AWS Firewall Manager
AWS Amplify
Amazon QuickSight
Amazon FSx
AWS Step Functions
AWS Global Accelerator
AWS DynamoDB Backups
AWS Transfer for SFTP Servers
Currently, these costs are lumped into the indirect cost item - ‘Other’. Going forward, costs associated with these services will be distributed into the following direct charges:
DataSync
Firewall Manager - Policies
Amplify - Build & Deploy
Amplify - Hosting
QuickSight - Reader
FSx - Backup
FSx - Data Transfer
FSx - Storage
FSx - Throughput
Step Functions - State Transition
Global Accelerator - Fixed Fee
Global Accelerator - Data Transfer
DynamoDB - Backup
Transfer for SFTP - Endpoint
Transfer for SFTP - Data Transfer
And the following indirect charges:
DataSync - Other
Firewall Manager - Other
Amplify - Other
QuickSight - Author
QuickSight - Other
FSx - Other
Step Functions - Data Transfer
Step Functions - Other
Global Accelerator - Other
Transfer for SFTP - Other
For the services mentioned above, we will be using AWS Tags, CloudHealth Tags, and Resource Id for cost and asset allocation. This allocation will be applicable to the past 13 months.
Learn more about supported AWS services in this Help Center article.