AWS Enterprise Support cost: the tiered percentage.
Enterprise Support is the largest single charge most enterprises never think to negotiate. It is priced as the greater of a $15,000 monthly minimum or a declining percentage of monthly AWS usage — a line that compounds on the entire bill. This note gives the formula, a worked example, how spend growth compounds the charge, the alternatives, and the levers that move it.
AWS Enterprise Support costs the greater of $15,000 a month or a tiered percentage of monthly usage — 10% of the first $150k, 7% to $500k, 5% to $1M, then 3% above. A $2M/month account pays about $94,500 a month, or $1.13M a year, before any negotiated reduction. Because it is a percentage of the bill, the two levers that matter are shrinking the usage base and negotiating the percentage down inside an EDP.
01 Key findings
Support is a percentage that compounds on the whole bill. Because it is metered against usage, every dollar of spend growth carries the support percentage stacked on top of it — making it one of the largest charges enterprises rarely scrutinise.
The formula is bracketed, not flat. The bands are cumulative like a tax bracket — 10% / 7% / 5% / 3% — so the blended effective rate falls as spend rises, and a $2M account pays a 4.7% blended rate, not 10%.
The percentage is negotiable inside an EDP. The $15,000 minimum is fixed, but the rate applied above it moves with committed spend; blended reductions to 2–5% are achievable at scale.
Gross versus net basis is a six-figure question. Whether support is calculated on gross usage or on usage net of the EDP discount can swing the annual charge by six or seven figures on a large account. The net basis is negotiable.
Many enterprises overbuy the tier. Enterprise On-Ramp delivers a pooled TAM and a 30-minute objective at a $5,500 minimum — a third of Enterprise — and fits estates whose recovery objectives are measured in hours, not minutes.
02 Support tiers
AWS sells four paid support tiers plus the free Basic tier. The jump that matters for enterprises is from Business to Enterprise, which adds a designated Technical Account Manager, a 15-minute response objective for business-critical incidents, and access to well-architected and operations reviews.
| Tier | Monthly cost basis | Response objective | TAM |
|---|---|---|---|
| Basic | Free | None (forums) | No |
| Developer | Greater of $29 or 3% | 12 hours (business) | No |
| Business | Greater of $100 or tiered 3–10% | 1 hour (production down) | No |
| Enterprise On-Ramp | Greater of $5,500 or tiered 3–10% | 30 min (business-critical) | Pooled |
| Enterprise | Greater of $15,000 or tiered 3–10% | 15 min (business-critical) | Designated |
03 The Enterprise Support cost formula
Enterprise Support is priced as the greater of a $15,000 monthly minimum or a declining percentage applied in bands to monthly AWS usage. The bands are cumulative, like a tax bracket, not a single flat rate on the whole bill.
| Monthly usage band | Marginal rate | Charge in band |
|---|---|---|
| First $0 to $150,000 | 10% | Up to $15,000 |
| $150,000 to $500,000 | 7% | Up to $24,500 |
| $500,000 to $1,000,000 | 5% | Up to $25,000 |
| Above $1,000,000 | 3% | 3% of the remainder |
04 Worked example
Take an account spending $2,000,000 per month on eligible AWS usage. The support charge is 10% of the first $150,000 ($15,000), plus 7% of the next $350,000 ($24,500), plus 5% of the next $500,000 ($25,000), plus 3% of the final $1,000,000 ($30,000). The total is $94,500 per month before any negotiated reduction — well above the $15,000 minimum. At $1,134,000 per year, support alone exceeds the entire AWS bill of many mid-market companies.
Support is a tax on the whole bill, not a fixed fee. Because it is a percentage of usage, the charge grows automatically as spend grows — without a single new negotiation or approval. Every dollar you add to the usage base carries the support percentage stacked on it, and every dollar you remove takes that percentage away. Committed compute through Reserved Instances and Savings Plans lowers the metered usage support is calculated against, so the support saving is an underappreciated second benefit of any commitment. Confirm whether your contract calculates support on gross or net usage; the difference is often six figures a year.
05 How spend growth compounds support cost
Because the charge is a percentage of usage, the monthly support bill climbs with the estate even when the tier never changes. The bars below show the monthly Enterprise Support charge at rising levels of monthly AWS usage — the same formula, compounding silently as spend grows.
The blended effective rate falls as spend rises — from 10% at $150k to 4.7% at $2M to 3.7% at $5M — but the absolute charge keeps climbing. Growth compounds the bill faster than the declining bands relieve it, which is why the largest support savings come from negotiating the percentage rather than waiting for the brackets to help.
06 Lower tiers and third-party alternatives
Beyond the percentage, the biggest structural saving is buying the right service level. AWS introduced Enterprise On-Ramp precisely because many customers paid full Enterprise rates for a response level their workloads never used. On-Ramp delivers a pooled rather than designated TAM, a 30-minute objective instead of 15 minutes, and a $5,500 minimum — roughly a third of Enterprise.
| Attribute | Enterprise On-Ramp | Enterprise |
|---|---|---|
| Monthly minimum | $5,500 | $15,000 |
| Critical response | 30 minutes | 15 minutes |
| TAM model | Pooled | Designated |
| Architectural reviews | Pooled access | Proactive, named |
| Best fit | Important, not life-critical | Business-critical, tight RTO |
AWS is also not the only source of enterprise support. Managed service providers and AWS Premier partners resell support bundled with their own managed services, often at an effective rate below AWS Enterprise for customers who already need the provider's operational help. The trade-off is the direct relationship: a partner intermediates between you and AWS, which can slow access to service teams during a severe incident and removes the named TAM who advocates internally during launches and negotiations. Assess the real recovery requirements honestly, then buy the support model that meets them rather than the most expensive one available.
07 Cost-control framework
Four levers reduce Enterprise Support cost. Work them in order — basis and tier first, because they are structural and repeat every month, then base reduction and the negotiated rate.
Confirm the calculation basis
Establish whether support is charged on gross usage or on usage net of the EDP discount. On a large account the difference between the two bases is six or seven figures a year, and the net basis is negotiable.
Right-size the tier
Organise accounts by criticality so Enterprise support sits only where recovery objectives justify it, and tier lower-criticality accounts down to On-Ramp. A default to the highest tier pays roughly three times the minimum for a response difference you will never use.
Shrink the usage base
Every dollar of Reserved Instance or Savings Plan coverage removes the support percentage stacked on it. Committed compute lowers the metered base support is calculated against — a second, underappreciated saving.
Negotiate the percentage
Inside an EDP the rate above the minimum moves with committed spend; blended reductions to 2–5% are achievable at scale. Time the support negotiation to coincide with the committed-spend negotiation so the two trade against each other.
08 Which support model to buy
You run frequent high-stakes launches or operate under strict regulatory recovery requirements. The designated TAM, 15-minute response and AWS-internal escalation path justify the premium. Negotiate the percentage and the net basis hard.
Your recovery objectives are measured in hours, not minutes. A pooled TAM, 30-minute objective and architectural reviews at a $5,500 minimum deliver the escalation path at a fraction of the cost. Frequently the right tier once workload risk is assessed honestly.
You already rely on a capable managed service provider. Folding support into that relationship can lower the effective rate, trading the direct TAM for the provider's intermediation — acceptable for steadier estates without minute-level recovery needs.
09 Negotiating the percentage
The support percentage is negotiable inside an EDP, and the larger the committed spend, the more it moves; reductions to a blended 2–5% are achievable at scale. Negotiate whether support is calculated on gross or net-of-discount usage, push for a tier-down to Enterprise On-Ramp where the risk profile allows, and time the support negotiation to coincide with the committed-spend negotiation so the two trade against each other. The full sequence is in our AWS EDP negotiation guide and the EDP pillar. For engagement, see our Cloud & FinOps practice and the AWS vendor hub.
Support is a percentage you can negotiate
Independent reviews cut enterprise support cost by a median of 26% without losing the TAM relationship.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.