IBM Cloudability

 View Only

 Distribute AWS Support refund

Jump to  Best Answer
  • Cloudability
Kevin King's profile image
Kevin King posted Tue September 26, 2023 11:24 AM

We use a business metric to distribute EDP credits from a monthly SP recurring fee back to the business.

Has anyone been able to distribute the monthly AWS support Refund back to their accounts? Support hits the payer account so not even sure if this is achievable in CLDY?


#Cloudability
Varad Rajeev Muthal's profile image
Varad Rajeev Muthal  Best Answer

Hi @Kevin King
Here is the answer to your query from @Alex Long

Do you have custom pricing enabled and can see a metric for cost adjusted? You shouldn’t need to use a custom business metric for that as it's standard CLDY functionality. It's not realistically possible to redistribute support charges with a metric.

Hope this will help you!


#Cloudability
Varad Rajeev Muthal's profile image
Varad Rajeev Muthal

Hello @Kevin King
I acknowledged your question and trying to find the best answer.


#Cloudability
Dustin Bowling's profile image
Dustin Bowling

Similar issue here.  No matter what Cost Metric is applied, all the Support charges hit the Payer Account and we do have custom pricing enabled and are on auto-EDP.  I've heard people using a Business Metric and a flat-rate multiplier to distribute the support charges back, but these won't be accurate if your algorithm is based on a % of spend.

I did ask our AWS account team to put in a feature request to calc the support charge in real-time at the member-account level, but not sure what the broader impacts would be and if this is even doable.  I know they are rolling out changes now with how support is billed (real-time vs. end of month).


#Cloudability
Dustin Bowling's profile image
Dustin Bowling

Hey Kevin,

One thing I'm attempting to do with a custom business metric is to calculate the % support allocation that assumes the credit has been applied, then zero out the actual credit in a business mapping where enahanced_service_name = "AWS Support" and transaction_type = 'credit;.  I'm not sure yet how successful this will be as I've never tried to build a Business Metric based on cost allocations that are synthetic dimensions (ie. Business Mappings).

You can see below where we set the default, zero out the support credit, don't apply support allocation to Marketplace software, and the credit offset is built in the multiplier 1.03565....  Every organization will have a different multiplier depending on agreement and spend levels, so you have to do the math in Excel first to figure out what it should be set to.  I also observed that it can fluctuate each month, so it's something to keep an eye on and tweak.

When I ran the math in Excel, it came out very close month over month against our invoiced amount, but not quite exact if you need to reconcile.  If so, you can perhaps absorb any shortages / overages in another cost center, or build in the delta in the following month, perhaps.

   "name": "Cost Center Chargeback (Billable)",
        "index": 1,
        "kind": "BUSINESS_METRIC",
        "defaultValue": "METRIC['total_amortized_cost'] * 1.0",
        "numberFormat": "currency",
        "updatedAt": "2024-01-24T01:07:02.654Z",
        "statements": [
            {
                "matchExpression": "BUSINESS_DIMENSION['billable cost center'] == 'AWS Enterprise Support'",
                "valueExpression": "METRIC['total_amortized_cost'] * 0.0"
            },
            {
                "matchExpression": "BUSINESS_DIMENSION['billable cost center'] == 'AWS Marketplace Contracts'",
                "valueExpression": "METRIC['total_amortized_cost'] * 1.0"
            },
            {
                "matchExpression": "BUSINESS_DIMENSION['billable cost center'] != 'undefined'",
                "valueExpression": "METRIC['total_amortized_cost'] * 1.03565"
            }
        ]
    }

Preliminary results look promising.   When I ran the math in Excel, it came out very close month over month against our invoiced amount, but not quite exact if you need to reconcile.  If so, you can perhaps absorb any shortages / overages in another cost center (the approach I'm going with), or build in the delta in the following month, perhaps.

The good thing is that I hear rumors AWS is going to start applying the support credit in real time, so we won't have to try and accommodate the separate credit memo after the month closes.  Now if I could get them to charge the net support bill at the linked / member account level.


#Cloudability