AWS support plans come in four tiers: Basic is free, Developer is a small fixed monthly minimum for non production guidance, and Business, Enterprise On Ramp, and Enterprise are priced as a tiered percentage of your monthly AWS usage subject to a monthly minimum. The percentage declines as spend rises but still scales with your bill, so the cost is driven by how much AWS you buy, not how much support you use. A large estate that opens few cases can therefore pay a substantial amount for support it barely touches. Two facts cut that bill: support is billed at the organization level so consolidating accounts avoids paying the minimum many times, and because the fee is a percentage, optimizing your AWS bill lowers the support fee at the same time.
Most enterprises land on Business or Enterprise support by default and never revisit it. Here is what each tier provides, where the percentage model bites, and how to decide.
What are the AWS support plan tiers?
There are two pricing shapes. Basic and Developer are simple, Basic free and Developer a low fixed monthly minimum. Business and the Enterprise tiers are the ones that carry real money because they are priced as a tiered percentage of usage.
| Plan | Pricing model | Fits |
|---|---|---|
| Basic | Included free | Documentation, billing, and account support only, no technical case support |
| Developer | Low fixed monthly minimum | Non production and experimentation, business hours guidance |
| Business | Tiered percentage of monthly usage, with a monthly minimum | Production workloads needing 24x7 technical support and full access to Trusted Advisor checks |
| Enterprise On Ramp | Higher percentage of usage, higher minimum | Production workloads wanting faster critical response and pooled technical account management |
| Enterprise | Highest percentage tier, highest minimum | Business critical estates wanting the fastest response and a designated technical account manager |
The percentage is tiered and declines as monthly usage climbs, but it never stops being a percentage of the bill. That is the structure to understand before you sign, and any specific percentage you have seen should be treated as indicative and confirmed against the current AWS support pricing page.
Why does percentage of spend support get expensive?
Business and Enterprise support are calculated from monthly AWS usage, so the bill is driven by how much you buy, not by how many cases you open. As the estate grows, the support fee grows in lockstep whether or not your support needs change. A team running a large, stable estate that opens a handful of routine cases a year can find a meaningful sum flowing to support every month for response capacity it almost never calls on.
The tiered decline softens this at the top end but does not remove it. Enterprise also bundles a technical account manager and proactive services that some organizations genuinely use and others never engage. The buyer question is whether you are paying for support you consume or for a percentage of a bill that happens to be large.
Pull twelve months of case history: volume, severity, and how often you needed fast escalation. If the support you actually used is small relative to the percentage you pay, you are paying for spend, not support, and a lower tier or tighter account structure wins.
How do you reduce AWS support cost without losing coverage?
Three levers, in order of effort. First, consolidate accounts under AWS Organizations so support is purchased once at the payer level. Support pricing applies to consolidated usage, and a sprawl of standalone accounts each carrying a monthly minimum is a common, avoidable overpay. Second, match the tier to behaviour: if you do not use the technical account manager or proactive Enterprise services, Enterprise On Ramp or Business may cover your real needs at a lower percentage. Third, and most powerful over time, lower the AWS bill itself. Because Business and Enterprise support are a percentage of usage, every dollar you remove through rightsizing, commitment coverage, and waste elimination also shrinks the support fee. The two savings compound.
A scaling fintech was on Enterprise support across several standalone accounts, each triggering its own monthly minimum, with case history that was modest and mostly routine. We consolidated the accounts under one organization so support was billed once on combined usage, moved the workloads that did not need the designated technical account manager to a lighter tier, and the broader optimization that lowered the AWS bill lowered the percentage based support fee alongside it. Right sizing support was part of the work that left the estate materially lighter. Figures are verified against billing data and anonymized.
Where this fits in the AWS estate
Support is one of several AWS costs that scale with spend rather than value and so reward periodic review. It sits alongside the other surprises and account structure decisions worth auditing. See common AWS billing surprises, how account design affects cost in multi account strategy and cost control, and how to untangle shared costs in untangling shared costs on AWS. The whole estate picture lives in the AWS cost optimization guide.
Frequently asked questions
What are the AWS support plan tiers?
How is Business and Enterprise support priced?
How do you reduce AWS support cost without losing coverage?
Right size your AWS support with us
We help enterprises test their AWS support tier against real case history, consolidate account structure, and lower the bill the support fee is a percentage of. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.