AWS Enterprise Support costs the greater of $15,000 per month or a tiered percentage of monthly AWS usage: 10 percent of the first $150,000, 7 percent to $500,000, 5 percent to $1,000,000, and 3 percent above $1,000,000, so a $2,000,000 per month account pays about $94,500 per month, and the percentage is negotiable inside an Enterprise Discount Program. Support is a percentage line that compounds on the entire bill, which makes it one of the largest single charges most enterprises never think to negotiate. This page gives the formula, a worked example, and the levers.
AWS 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 to 10% | 1 hour (production down) | No |
| Enterprise On-Ramp | Greater of $5,500 or tiered 3 to 10% | 30 min (business-critical) | Pooled |
| Enterprise | Greater of $15,000 or tiered 3 to 10% | 15 min (business-critical) | Designated |
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 |
Worked example
Take an account spending $2,000,000 per month on eligible AWS usage. The support charge is 10 percent of the first $150,000 ($15,000), plus 7 percent of the next $350,000 ($24,500), plus 5 percent of the next $500,000 ($25,000), plus 3 percent 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.
The base-reduction lever: Because support is a percentage of usage, every dollar you remove from the usage base also removes the support percentage stacked on it. Committed compute through Reserved Instances and Savings Plans lowers the metered usage that support is calculated against, so the support saving is an underappreciated second benefit of any commitment. Conversely, the flat EDP discount does not reduce the support base in the same way, so confirm whether your contract calculates support on gross or net usage; the difference is often six figures a year.
What the Enterprise tier includes
The Enterprise tier buys a designated Technical Account Manager, the fastest response objective AWS offers, infrastructure event management for launches, well-architected reviews, and concierge billing support. For organizations running business-critical workloads with tight recovery objectives, the TAM relationship and 15-minute response have real operational value. For steady-state estates without that profile, Enterprise On-Ramp delivers a pooled TAM and a 30-minute objective at a lower minimum, and is frequently the right tier once the workload risk is assessed honestly.
Enterprise versus Enterprise On-Ramp
AWS introduced Enterprise On-Ramp as a middle tier precisely because many customers were paying full Enterprise rates for a service level their workloads did not require. On-Ramp delivers a pooled rather than designated Technical Account Manager, a 30-minute response objective for business-critical cases instead of 15 minutes, and a lower $5,500 monthly minimum. For an estate whose recovery objectives are measured in hours rather than minutes, On-Ramp provides the architectural reviews and the escalation path at a fraction of the Enterprise cost.
| 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 |
The decision between the two should follow a sober assessment of recovery objectives, not a default to the highest tier. Many enterprises carry Enterprise support out of habit on workloads that would be perfectly served by On-Ramp, paying roughly three times the minimum for a response-time difference they will never use.
What the TAM relationship delivers
The designated Technical Account Manager is the core of what the Enterprise tier sells, and its value is real but uneven across customers. A TAM who knows your architecture accelerates incident resolution, brokers access to service teams during launches, runs well-architected reviews that surface cost and reliability issues, and acts as an advocate inside AWS during escalations and negotiations. For an organization running frequent high-stakes launches or operating under strict regulatory recovery requirements, that relationship justifies the premium. For a steady-state estate that rarely opens a critical case, the TAM is an expensive insurance policy whose value is mostly latent.
Reducing support without losing coverage
Beyond tier choice, two structural moves reduce support cost. The first is confirming whether support is calculated on gross usage or on usage net of the EDP discount; on a large account the difference between the two bases can be six or seven figures a year, and the net basis is negotiable. The second is reducing the metered usage base itself through committed compute, since support is a percentage of usage and every dollar of Reserved Instance or Savings Plan coverage removes the support percentage stacked on it. Managed service providers also resell AWS support bundled into their own offering, which can lower the effective rate for customers already paying an MSP, though it trades the direct TAM relationship for the provider's intermediation.
Third-party and partner support
AWS is not the only source of enterprise support, and the alternatives change the cost calculus for some estates. 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. Independent cloud-operations firms offer break-fix and architectural support outside the AWS tiers entirely. The trade-off is the direct relationship: a partner intermediates between you and AWS, which can slow access to AWS service teams during a severe incident, and it removes the named TAM who advocates inside AWS during launches and negotiations. For estates whose risk profile genuinely requires the 15-minute response and the AWS-internal escalation path, the direct Enterprise relationship is worth its premium. For steadier estates already paying a capable MSP, folding support into that relationship can lower the effective cost without meaningful loss.
The decision should follow the same logic as the tier choice: assess the real recovery requirements honestly, then buy the support model that meets them rather than the most expensive one available. Many enterprises carry full Enterprise support out of caution on workloads a lower tier or a partner model would serve perfectly well.
Frequently asked questions
Is the $15,000 minimum negotiable?
The minimum itself is fixed, but the percentage applied above it is negotiable inside an EDP, and at scale the blended effective rate can fall well below the published bands. The larger the committed spend, the more the percentage moves.
Is support charged on gross or discounted usage?
It depends on the contract, and the difference is large. Confirm whether your agreement calculates the support percentage on gross usage or on usage net of the EDP discount, because the net basis can save six or seven figures a year on a large account.
Can I drop from Enterprise to Enterprise On-Ramp?
Yes, and many estates should. On-Ramp delivers a pooled TAM and a 30-minute critical response at a $5,500 minimum, roughly a third of Enterprise, and suits workloads whose recovery objectives are measured in hours rather than minutes.
Right-sizing support to workload tiers
The most common support overpayment comes from applying one support tier uniformly across an estate whose workloads have very different criticality. A production payments system and a batch analytics job do not need the same response objective, yet a single account-level support tier charges as if they do. While AWS support is purchased per account rather than per workload, the architectural response is to organize accounts by criticality, so that the workloads requiring Enterprise-grade response sit in accounts carrying Enterprise support and the lower-criticality workloads sit in accounts on a cheaper tier. A well-designed account structure can therefore reduce total support cost substantially by ensuring the expensive tier is paid only where the recovery objectives justify it. This is a structural decision that pays back every month, and it is one of the few support levers fully within the customer's control.
Support and the well-architected program
The Enterprise and On-Ramp tiers include access to well-architected reviews, and these are worth using rather than leaving on the shelf. A well-architected review frequently surfaces cost-optimization findings, idle resources, over-provisioned instances, and missing commitment coverage, that pay for a meaningful fraction of the support fee itself. Treating the support relationship as a cost-reduction resource rather than only an incident-response insurance policy changes its return: the TAM and the review program can be directed at finding savings, which is exactly the work that lowers the usage base support is then charged on. Customers who use the program actively extract more value from the same support spend than those who hold it purely for emergencies.
How to negotiate support cost
The support percentage is negotiable inside an EDP, and the larger the committed spend, the more it moves; reductions to a blended 2 to 5 percent 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 contract negotiation service and the AWS vendor hub.