CloudHealth 'apportioning' process and impact to how dedicated host costs are categorized in the user interface
search cancel

CloudHealth 'apportioning' process and impact to how dedicated host costs are categorized in the user interface

book

Article ID: 284029

calendar_today

Updated On:

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.  EC2 dedicated host costs are apportioned in the chart but not in the drill-down.

Resolution

  1. Dedicated Host Costs: There are two main costs associated with Dedicated Hosts: EC2 - Dedicated Hosts Unused Cost and EC2 - Dedicated Host Instances. The platform only attributes costs to the Dedicated Host itself, not to the instances running on it.
  2. CloudHealth's Goal: CloudHealth distributes the cost of the Dedicated Host across the instances running on it and tries to separate out an "unused" cost for the Dedicated Host itself to bring a clearer view of these charges.
  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.  The process is called "apportioning." It's only visible in the user interface (UI) of the report, not in detailed drill-downs.  Compute costs are categorized under "Compute."