What cloud support costs: the spend percentage against a flat monthly fee

The bill is the greater of two numbers, and spend decides which

AWS sells three support plans: Business Support+, Enterprise Support and Unified Operations. Each is billed monthly with no long-term contract, and each is priced as the greater of a specified minimum monthly fee or a percentage of your monthly AWS charges. That single sentence is the whole pricing model, and it means the plan you pick sets a floor while your bill sets the ceiling.

The percentage is calculated on each month's gross AWS charges, before any discounts or credits are applied. A team that has negotiated an enterprise discount will still pay support on the pre-discount number. The page also excludes a list of services from the calculation entirely, among them AWS Support itself, AWS Managed Services, AWS Professional Services, AWS Training and Certifications, Amazon EKS Anywhere and VMware Cloud on AWS.

Business Support+ fees are calculated per account. Enterprise Support and Unified Operations are billed on the aggregate monthly gross charges across all account IDs subscribed to that plan, which matters to an organisation running a landing zone with dozens of accounts: the percentage is applied once to the total, not account by account.

Every plan carries a minimum commitment of 30 days, except Unified Operations, which requires 90. Cancel mid-month after the minimum and AWS prorates a refund for the remainder of the month, subject to the plan's minimum monthly charge. AWS reserves the right to refuse support to a customer that frequently signs up and cancels.

What the percentage actually buys at each tier

The tier sets the response time, and the page states them for Azure's plans rather than AWS's: critical business system down is answered within 15 minutes for Azure and one hour for all other products on the top tier, while minimal business impact is answered within eight business hours on the lower tiers and four on the higher ones. A buyer comparing the two clouds should ask AWS for the equivalent severity matrix in writing, because the AWS pricing page does not print one.

Enterprise Support carries two named add-ons. AWS Incident Detection and Response gives 24x7 proactive engagement and five-minute response times for incident management, available to Enterprise Support customers at a minimum spend of $7K or 2% of aggregated monthly AWS charges in enrolled accounts. AWS Countdown Premium provides planning, designated engineering support and real-time assistance for launches, migrations and peak traffic, at $10K per project per month for Business Support+ and Enterprise Support customers.

Unified Operations includes both at no additional cost. That is the tier where the bundle stops being a percentage and starts being a package, and it is the one to price carefully against Enterprise Support plus the two add-ons bought separately.

The Azure page shows the same architecture of tiers with a different set of inclusions: advisory support, service reviews and expert-led engagements sit behind a Flex Allowance or add-on purchases, and third-party software support with interoperability guidance is not included on the lower plans. Neither vendor bundles everything, and the inclusions are where the two plans diverge most.

The components, and what each costs on its own

Read the AWS page as a decomposition rather than a price list. The base plan is a percentage of spend with a minimum. Incident Detection and Response is a second percentage with a $7K floor, charged on enrolled accounts. Countdown Premium is a flat $10K per project per month, billed from the start date the customer gives at registration. Unified Operations folds the first two in and adds a 90-day minimum commitment.

The table sets out what is metered, what is bundled and what is charged separately, using only the figures the pages publish.

Two mechanics move the number more than the tier choice. Prepaid Savings Plans, Reserved Instances and Nodes are included in the support fee calculation in the month you purchase them, so a large upfront commitment produces a support charge in the same month. And if you hold reserved resources when you sign up, the upfront charges are prorated over the reservation term and included in the first month's fee.

The Azure page adds a billing detail worth checking on the other side: support plans are billed monthly and renew automatically, Azure Prepayment dollars cannot be applied to them, and cancelling a support plan does not produce a prorated refund. AWS prorates after the minimum period; Azure, on its published terms, does not.

Where the percentage model stops being the cheap option

On a $50,000 monthly AWS bill, the percentage is the line that gets paid, not the floor, because the published minimums sit well below that level. The page does not print the percentage rates themselves, so the exact figure at $50,000 is unpublished. Ask the account team for the rate card by plan and the minimum monthly fee for each, in writing, before modelling the renewal.

The regional pricing structure is the other unpublished variable. Customers qualify for regional pricing if all accounts on their billing profile are concentrated in qualified LATAM countries, India or Mainland China, subject to conditions, and the fee is then the greater of a $5K minimum monthly fee or tiered pricing based on monthly charges. A multinational with accounts spread across regions should confirm which billing profile each account sits on before assuming the standard rate applies.

The exclusions list is where a percentage model can mislead a budget holder in the other direction. Spend on AWS Marketplace, professional services and training does not count toward the support fee, so a team that shifts licence purchases to Marketplace lowers its support charge without lowering its total cloud spend. That is a legitimate lever, and it is worth naming in the renewal conversation.

The Azure page shows the alternative shape: a named plan with a published set of inclusions and a Flex Allowance that can be applied to specialised services. Neither vendor publishes a single comparable number, which is why the comparison has to be run on the reader's own bill rather than on a rate card.

What to ask before signing

Ask for the severity and response-time matrix for each plan, since the AWS pricing page does not print one and the Azure page does. Ask for the percentage rate that applies to your spend band and the minimum monthly fee for each plan. Ask which of your accounts would be aggregated under Enterprise Support and whether any qualify for regional pricing.

Ask how prepaid commitments bought in the current quarter will land in the support fee, because the page states they are included in the month of purchase. Ask whether Incident Detection and Response enrolment is per account or per billing profile, since the $7K or 2% minimum is calculated on enrolled accounts.

Then ask what happens at cancellation. AWS prorates after the 30-day minimum; Unified Operations holds you for 90 days. A team that expects to run a short migration and then step down should price the 90-day tail into the decision.

Who should walk away

Walk away from Enterprise Support if your monthly bill is small enough that the minimum fee, not the percentage, is what you pay, because you are buying a floor rather than a service level. Walk away from Unified Operations if you cannot commit to 90 days, since the plan's inclusions are worth little against a term you will not serve.

Walk away from Countdown Premium if the launch it covers is a one-off and the $10K per project per month is larger than the engineering time it replaces. And walk away from any of these plans if the workload is not business-critical: the Azure page is explicit that its lower tiers exist for small and medium-size companies, and the same logic applies on the other side of the comparison.