How does CloudHealth's 'apportioning' process work, and how does it impact the way dedicated host costs are categorized in the user interface?

Products

• CloudHealth

Issue/Introduction

It's expected that the Dedicated host cost (both unused and instance cost) won't match between the chart and the drill-down, as the EC2 dedicated host costs are apportioned in the chart but not in the drill-down.

1. Dedicated Host Costs: There are two main costs associated with Dedicated Hosts: EC2 - Dedicated Hosts Unused Cost and EC2 - Dedicated Host Instances. However, when we look at the bill, it only attributes costs to the Dedicated Host itself, not to the instances running on it.
2. CloudHealth's Goal: Our goal with CloudHealth is to distribute the cost of the Dedicated Host across the instances running on it. Additionally, we want to separate out an "unused" cost for the Dedicated Host itself.
3. Dedicated Host Unused Cost: This is the total cost of the unused slots on the Dedicated Host throughout the billing period.
4. Dedicated Host Instance Cost: This is the cost of the Dedicated Host, divided by its total capacity, giving us the cost per instance.
5. Apportioning: AWS doesn't break down costs related to Dedicated Hosts in the bill, so CloudHealth does this every month. We call this process "apportioning." It's only visible in the user interface (UI) of the report, not in detailed drill-downs. We take the compute cost and categorize it under "Compute."