FOCUS #406 (v1.1 draft): Extend CommitmentDiscountCategory column to categorize on-demand row eligibility for commitments

[cnharris10]

Extend column: CommitmentDiscountCategory provide visibility into commitment-based coverage potential.

A CommitmentDiscountCategory value exists when (assuming a Savings Plan):

1. ChargeCategory: Purchase --> CommitmentDiscountCategory: Spend
2. ChargeCategory: Usage, ChargeSubCategory: Used --> CommitmentDiscountCategory: Spend
3. ChargeCategory: Usage, ChargeSubCategory: Unused --> CommitmentDiscountCategory: Spend

To help practitioners derive Commitment Coverage potential to determine how much more savings is possible, this pr extends CommitmentDiscountCategory with the following scenarios where CommitmentDiscountId is null:

Scenario 4: AWS EC2 VM is eligible for an Reserved Instance or Savings Plan, so Multiple is assigned

• ChargeCategory: Usage
• ChargeSubCategory: On-Demand
• SkuId:
  --> CommitmentDiscountCategory: Multiple

Scenario 5: AWS RDS VM is eligible for a Reserved Instance (only), so Usage is assigned

• ChargeCategory: Usage
• ChargeSubCategory: On-Demand
• SkuId:
  --> CommitmentDiscountCategory: Usage

Scenario 6: AWS Lambda is eligible for a Savings Plan (only), so Spend is assigned

• ChargeCategory: Usage
• ChargeSubCategory: On-Demand
• SkuId:
  --> CommitmentDiscountCategory: Spend

With these additional scenarios, practitioners can calculate their commitment coverage rate (and drill down) as:

(SELECT SUM(ChargePeriodEnd - ChargePeriodStart) FROM <table> WHERE CommitmentDiscountCategory IS NOT NULL AND ChargeSubCategory = 'Used') 
/
(SELECT SUM(ChargePeriodEnd - ChargePeriodEnd) FROM <table> WHERE CommitmentDiscountCategory IS NOT NULL AND ChargeSubCategory IN ('Used', 'On-Demand'))
* 100

[jpradocueva]

Comments from Members' call on Oct 31:

Analysis: Opened to clarify eligibility requirements for on-demand resources with commitments. The resolution hinges on determining overall direction for eligibility.
Agreements: Keep #407 open while confirming eligibility requirements during 1.2 discussions.