A data center aisle lined with server racks
AWS Enterprise Support

AWS Enterprise Support pricing in 2026. How the bands work and where to negotiate.

The four Enterprise Support fee bands, the new $5,000 minimum, what AWS counts in the fee base, what the TAM is worth and how to bring support into your EDP.

Contact Us Negotiation Advisory
500+Enterprise clients
$2B+Under advisory
PublishedMarch 5, 2025UpdatedSeptember 24, 2026
ContentsKey takeawaysHow the fee bands workCost at different spend levelsIs the TAM worth itSupport inside the EDPWhat we have seenNegotiation tacticsBy company sizeAlternative support plansCheck what you payHow Redress helpsWhat to do nextFAQ

Enterprise Support costs 10 percent of the first $150,000 of monthly AWS charges, falling to 3 percent above $1M, with a $5,000 minimum. The rate is published, but the fee base, discount and TAM terms are negotiable inside your EDP.

Key takeaways
  • Four bands, not one rate. AWS charges 10 percent on the first $150k of monthly spend, 7 percent to $500k, 5 percent to $1M and 3 percent above $1M.
  • The minimum fell to $5,000. Small AWS accounts paid a $15,000 monthly floor whatever they consumed until AWS cut it in December 2025.
  • The fee base is gross. Support is calculated before EDP discounts and credits, while Reserved Instances and Savings Plans lower it by lowering the charges themselves.
  • The TAM is only worth what you schedule. A designated Technical Account Manager can save real consumption through reviews and cost guidance, but only if the cadence is agreed and used.
  • Negotiate support inside the EDP. Support spend can count toward the commitment and the discount can reach the support line, if both are written into the deal.
  • Marketplace stays out of the base. AWS excludes Marketplace spend from the support calculation, except Bedrock purchases, and your agreement should say so.
  • An outside benchmark lowers the rate. Buyers with an independent benchmark ended up 3 to 5 percentage points lower on blended support rate than those without one.

AWS Enterprise Support is billed as a sliding percentage of your monthly AWS charges: 10 percent of the first $150,000, 7 percent up to $500,000, 5 percent up to $1,000,000 and 3 percent above that. A monthly minimum applies. AWS cut that minimum from $15,000 to $5,000 when it reworked its support plans in December 2025.

  • Large bills. Because the rates step down, the blended rate sits well below the 10 percent headline.
  • Small bills. The minimum can push the blended rate above 10 percent.
  • Timing. Negotiate support inside the commitment deal rather than after it.

This guide belongs to our AWS knowledge hub and our AWS advisory practice. For the commitment side, read the AWS EDP negotiation guide; for choosing between plans, read AWS support plan negotiation.

How does AWS Enterprise Support tiered pricing work?

Each rate applies only to the slice of monthly spend inside its band, like income tax brackets. You pay 10 percent on the first $150,000, then 7 percent on the next $350,000, and so on. AWS charges the greater of that tiered total or the monthly minimum.

AWS Enterprise Support fee bands (monthly AWS charges)
Monthly AWS chargesMarginal support rateFee at top of bandBlended rate at top of bandWhat to check
$0 to $150,00010%$15,00010.0%Monthly minimum ($5,000 now, $15,000 before December 2025)
$150,000 to $500,0007%$39,5007.9%Which accounts are aggregated into the bill
$500,000 to $1,000,0005%$64,5006.45%Upfront commitment purchases that spike one month
Above $1,000,0003%$184,500 at $5MBelow 5% from about $1.73MSupport terms in the EDP

The old $15,000 minimum was exactly the fee on $150,000 of spend, so any customer below that level paid more than 10 percent. Under the $5,000 minimum the floor only binds below $50,000 of monthly charges.

What changed in the December 2025 support plan overhaul?

On December 2, 2025, AWS restructured its support catalog. The Enterprise Support bands stayed the same, but the minimum dropped to $5,000 and AWS Security Incident Response is now included at no extra cost. AWS also added two plans around it.

  • Business Support+. From $29 per account per month, tiered from 9 percent down to 3 percent, with a 30 minute response on critical cases and no TAM.
  • Unified Operations. From $50,000 per month, at 10 percent of the first $1M, 6 percent to $5M and 5 percent above, with a 5 minute critical response and a team that adds a domain engineer and a billing specialist to the TAM.
  • Retirements. Developer, Business and Enterprise On-Ramp reach end of support on January 1, 2027. On-Ramp customers are being moved to Enterprise Support, many of them at their 2026 renewal.

If you are on On-Ramp today, read our note on the Enterprise On-Ramp retirement before AWS schedules the upgrade for you. For contracts that run past 2027, the support tier restructuring clause covers the wording.

Which charges count toward the support fee?

AWS calculates the fee on each month's gross charges, before discounts or credits. That detail costs more than most buyers expect, because your EDP discount and any migration credits do not shrink the base.

  • Counted. Normal usage at the rates on pages such as AWS EC2 pricing, plus Reserved Instance and Savings Plans charges. Upfront payments count in full in the month you make them.
  • Excluded. AWS Marketplace, AWS Professional Services, AWS Managed Services, Training and Certification, VMware Cloud on AWS and support itself, among others on the published list.
  • The Marketplace exception. Bedrock Marketplace and Bedrock serverless purchases count as Bedrock usage, even when they appear on a Marketplace bill.
  • Which accounts. Enterprise Support is billed on the combined gross charges of every account ID subscribed to it. The accounts you subscribe decide how much spend reaches the cheaper bands. Business Support+, by contrast, is calculated account by account.

Reserved Instances and Savings Plans still lower the fee over time. Committed rates are below On-Demand, so the same workload produces smaller gross charges and a smaller support line. See Savings Plans versus Reserved Instances for choosing between them.

Watch the briefingEpisode 9 of 12 · 4:38

What does Enterprise Support cost at different spend levels?

The fee grows much more slowly than the bill once you pass $150,000 a month. The table below applies the published bands to five hypothetical monthly bills, with no discount on the support line.

Worked example: Enterprise Support fee by monthly AWS charges
Monthly AWS chargesHow the fee buildsMonthly feeBlended rateAnnual fee
$80,00010% of $80,000 (old minimum would have been $15,000)$8,00010%$96,000
$300,000$15,000 + 7% of $150,000$25,5008.5%$306,000
$750,000$15,000 + $24,500 + 5% of $250,000$52,0006.93%$624,000
$2,000,000$64,500 + 3% of $1,000,000$94,5004.73%$1,134,000
$5,000,000$64,500 + 3% of $4,000,000$184,5003.69%$2,214,000

The $80,000 row shows what the minimum change did: under the $15,000 floor that customer paid 18.75 percent of spend for support.

The most common tiered pricing mistake

Finance teams see the 10 percent headline and apply it to the whole bill. On a $2M monthly bill that forecast says $200,000 a month, while the real fee is $94,500. The error is $105,500 a month, or about $1.27M a year.

An inflated baseline hurts you twice. It makes any AWS concession look larger than it is, and it hides how much of the fee comes from the first two bands, where the rates are highest: on the $2M bill, $39,500 of the $94,500.

Is the technical account manager worth what you pay?

Only if you schedule and use the proactive work. The designated Technical Account Manager is what separates Enterprise Support from the cheaper plans, alongside the 15 minute response on business critical cases.

Six TAM benefits to put a value on

  • Well-Architected reviews. Two to four reviews a year, scored against the six Well-Architected pillars (AWS added sustainability as the sixth in 2021).
  • Cost optimization guidance. Reserved Instance and Savings Plans recommendations based on your live workload.
  • Architecture reviews. Reviews of major workloads before they go live.
  • Incident drills. Tabletop exercises and incident response drills with your operations team.
  • Service team escalation. A direct path to the AWS service teams when a case stalls.
  • Roadmap access. Briefings on AWS service roadmaps under NDA.

Since the 2025 overhaul, Enterprise Support also includes AWS Security Incident Response. If you pay a third party for incident response, price the overlap.

The most common TAM mistake

Companies sign up for Enterprise Support and then use the TAM only to route reactive cases. The proactive reviews go unused, so the return on the fee falls. Agree the TAM cadence at signing: a named quarterly calendar of reviews, with dates, owners and a written summary after each one.

How do you fold support into an Enterprise Discount Program?

Negotiate the support line and the EDP commitment at the same time, in the same document. Support spend can count toward the commitment and the EDP discount can apply to the support charge, if the agreement says so. AWS now often papers the EDP as a Private Pricing Agreement (PPA), which works the same way.

Why support belongs inside the EDP

Most customers model Enterprise Support as a fixed percentage outside the EDP, then raise it after the commitment is agreed, when AWS has nothing left to trade for. When we run the EDP and support as one conversation, the combined discount comes out 3 to 5 percentage points higher than negotiating them one after the other.

Five EDP terms to ask for on Enterprise Support

  1. Support counts toward the commitment. Ask for the full support line to be included in the spend that retires your commitment.
  2. The discount reaches support. Negotiate the EDP discount against the support charge as well as usage.
  3. The tier reopens at renewal. Put the support rate on the agenda at every renewal, including this one.
  4. Marketplace stays out. Confirm in writing that Marketplace spend is excluded from the support base, with the Bedrock exception spelled out.
  5. Commitments line up. Make Reserved Instance and Savings Plans terms coterminous with the EDP and the support term.

A hypothetical example shows why the second term matters. At $2M a month, the fee is $1,134,000 a year on gross charges. A 10 percent EDP discount on usage leaves that fee untouched, because the base is gross. The same 10 percent applied to the support charge saves $113,400 a year.

What have we seen in recent AWS Enterprise Support negotiations?

Across roughly 25 to 35 AWS commitment reviews I ran in 2024 and 2025, customers treated Enterprise Support as a fixed tax on the bill, when in most deals its terms were open. Three patterns came up again and again.

  • Size of the line. Support ran 3 to 10 percent of total AWS spend, rising with the bill whatever value was delivered.
  • Effect of the EDP. Folding support into the Enterprise Discount Program cut the effective support rate by 15 to 30 percent.
  • Unused TAM capacity. Designated technical account hours went 40 to 70 percent unused against what was paid for.

Buyers who benchmarked the EDP independently ended up with a blended support rate 3 to 5 percentage points below those who had no outside benchmark.

Why we do not accept that support is a fixed percentage

The account team usually presents Enterprise Support as a published rate that is not open for discussion. We disagree with taking that at face value. In most of the reviews above, support already sat within the scope of the EDP and the terms improved once the customer asked.

Price support as part of the total commitment, compare the TAM value with the hours actually used, and table the support terms with everything else. Check the published bands on the AWS Enterprise Support plan page before you accept a renewal quote.

A spreadsheet cost model open on a computer screen
Rebuild the support fee from your own billing data before the renewal call. AWS bills on gross charges, so a model built on discounted spend will understate what you pay.
Most AWS support overspend sits in technical account hours that never get scheduled, rather than in the headline rate.

Which negotiation tactics lower the AWS support fee?

Four tactics reliably lower the fee or raise what you get for it: moving non production accounts off Enterprise Support, naming the TAM, writing the review cadence into the order and adding a deflator. Each works best when raised inside the EDP negotiation.

Four tactics for the support line

  • Carve out non production accounts. Negotiate a lower tier or plan for development and test accounts.
  • Specify the TAM. Ask for a senior TAM with experience in your industry, named in the order.
  • Fix the proactive cadence. Agree a quarterly schedule of Well-Architected, cost optimization and architecture reviews.
  • Add a deflator. Ask for a lower support rate if AWS consumption falls materially, so the fee follows the bill downward as well as up.

What the account team will say, and what to say back

  • "Support pricing is published and the same for everyone." The bands are published. Whether support counts toward the commitment and whether the discount applies to it are deal terms, and we want them in this deal.
  • "The TAM more than pays for itself." Then commit to the cadence in writing. Show us the reviews delivered in the last 12 months and we will value them against the fee.
  • "Moving dev and test to a cheaper plan loses you the aggregated rate." Send us the fee both ways. If the split saves money after the band effect, we will take it.
  • "You can revisit support at the next renewal." Support terms left out of this EDP stay out until it expires, so we settle them now.

Contract wording to ask for

  • Fee base definition. State which charges count and list the exclusions, including Marketplace, so a change to AWS policy mid term does not raise your fee.
  • Discount scope. List the support charge among the charges the EDP discount applies to. If it is not listed, the discount does not reach that line.
  • TAM service description. Record the review cadence and a replacement right if the named TAM leaves or underdelivers.
  • Plan change rights. Keep the right to move accounts between plans during the term without reopening the EDP.

How does the right support plan change with company size?

Monthly spend decides most of it, followed by how much of that spend runs production.

Below $150,000 a month

Under $50,000 of monthly charges the $5,000 minimum sets your price; from there to $150,000 you pay a flat 10 percent. Compare Enterprise Support with Business Support+, which starts at $29 per account and charges 9 percent on the first $10,000. If you do not need a TAM or the 15 minute response, Business Support+ will usually cost less.

From $150,000 to $1M a month

Here the support line becomes a real budget item. Most of the fee still comes from the 10 and 7 percent bands, so eligible spend and discount scope matter more than the marginal rate.

Above $1M a month

Past $1M the marginal rate is 3 percent. If AWS proposes Unified Operations, note that its 6 percent band from $1M to $5M costs twice as much per dollar, in exchange for a larger team.

What are the alternatives to AWS Enterprise Support?

AWS now sells three plans, and three older plans run until January 1, 2027. Third party AWS Premier consulting partners are the other option, usually for hybrid operations.

AWS support plans compared
PlanPricingCritical responseTAM includedBest for
Enterprise SupportTiered 3 to 10%, $5,000 minimum15 minutesYes, designated TAMProduction and business critical workloads
Unified OperationsTiered 5 to 10%, $50,000 minimum5 minutesYes, plus wider teamVery large, operations heavy customers
Business Support+Tiered 3 to 9%, $29 minimum per account30 minutesNoProduction without a TAM
Enterprise On-Ramp (ends January 1, 2027)10% or $5,500 minimum30 minutesPool of TAMsMid market enterprise
Business Support (ends January 1, 2027)Tiered 3 to 10%, $100 minimum1 hourNoProduction, non critical
Developer Support (ends January 1, 2027)3% or $29 minimum12 business hoursNoDevelopment only
Premier PartnerNegotiatedPartner SLAPartner architectHybrid management

Splitting production and non production accounts

Support plans attach to account IDs, so production can stay on Enterprise Support while sandboxes and test environments move to the cheaper plan. AWS recommends one plan across the organization, so expect resistance. Each dollar moved out leaves the lowest band first, so price the split before you ask.

How do you check what you pay for support today?

Start from your own billing data before you look at the AWS quote.

  1. Cost Explorer. Group by service and read the support line for the last 12 months.
  2. Cost and Usage Report. Filter support line items to see which accounts carry the fee and which months upfront purchases inflated.
  3. Your AWS Organizations account list. Mark each account production or non production and note its plan.
  4. The EDP or Private Pricing Agreement. Find the wording on eligible spend, discount scope and exclusions.
  5. The TAM activity record. Ask for the reviews, drills and briefings delivered last year.

Amazon reports AWS as its own segment, with its own operating income, in the annual Amazon 10-K filings. That is useful context when you hear that support margins leave no room to move.

Renewal timeline for the support line

When to work on Enterprise Support before an EDP renewal
Before renewalWhat to do
12 monthsPull 12 months of support charges, map accounts to plans and request the TAM activity record.
6 monthsModel the fee under the bands, with and without the non production split, and set your targets for eligible spend and discount scope.
3 monthsPut the support terms into the EDP proposal alongside the commitment.
1 monthCheck the fee base definition, the TAM cadence and the deflator in the draft before signature.

How does Redress help with AWS Enterprise Support?

We work on AWS support inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program and the Software Spend Assessment. AWS commercial work is led by the founders.

Our benchmarking page explains how we compare your terms with recent deals. You can read about us, find our offices on the locations page or contact us directly.

What to do next

  1. Model the bands. Apply the four bands and the $5,000 minimum to projected gross monthly charges.
  2. Audit the TAM. Compare the reviews and proactive sessions offered with those delivered.
  3. Model the EDP with support inside. Run the commitment with and without the support spend counted, and with the discount applied to support.
  4. Split non production. Price development and test accounts on Business Support+ and decide at signing.
  5. Confirm the Marketplace exclusion. Get the exclusion, and the Bedrock exception, written into the agreement.
  6. Add the deflator. Ask for a lower support rate if AWS consumption falls materially.
  7. Get an outside benchmark. Benchmarks from AWS favor AWS; an independent one shows where your terms sit.

Frequently asked questions

What is the AWS Enterprise Support pricing structure?

The greater of a $5,000 monthly minimum or a banded fee: 10 percent of the first $150,000 of monthly charges, 7 percent from $150,000 to $500,000, 5 percent from $500,000 to $1,000,000 and 3 percent above. Older quotes may still show the $15,000 minimum that applied before December 2025.

What does the Technical Account Manager deliver?

Well-Architected reviews, cost optimization advice, architecture reviews before major launches, incident drills, escalation to AWS service teams and roadmap briefings under NDA. Enterprise Support now also bundles AWS Security Incident Response. Write the review cadence into the order at signing so the sessions actually happen.

Does Enterprise Support count toward the EDP?

It can, depending on how the agreement defines eligible spend. Ask for the support charge to count toward the commitment and to be listed among the charges the EDP discount applies to. Because AWS bills support on gross charges, a usage discount alone never reduces the support line.

Can I exclude non production accounts from Enterprise Support?

Yes. Enterprise Support is billed on the combined charges of the account IDs subscribed to it, so you can leave development and test accounts on Business Support+. AWS recommends one plan across the organization, so expect pushback. Price both options first, since removed spend comes out of the lowest band.

Is Marketplace consumption included in the support calculation?

No. AWS lists Marketplace among the charges excluded from the support fee, except Bedrock Marketplace and Bedrock serverless purchases, which count as Bedrock usage. Put the exclusion into the master agreement as well as the order form, so a later policy change cannot pull Marketplace spend into the fee.

How does Redress engage on AWS Enterprise Support?

Through Vendor Shield, the Renewal Program, the Benchmark Program or a Software Spend Assessment. We model your fee from billing data, audit TAM delivery, draft the EDP support terms and Marketplace language, and support the renewal negotiation. We work only for buyers and take no payment from AWS.

Is AWS Enterprise Support a fixed percentage?

The bands are fixed on the price list, but what you pay is not. Whether support counts toward your commitment, whether the discount applies to it and which accounts are aggregated are all deal terms. Buyers who raise support as part of the total commitment usually improve the effective rate.

What does an AWS technical account manager actually provide?

One named person who learns your environment, gives proactive guidance and escalates stuck cases. Track the reviews and hours you actually receive over a year and compare them with the support fee before you renew.

Newsletter
Licensing news that changes what you pay

One email a week on vendor price moves, audit activity and what worked in recent renewals.

Subscribe
Vendor Shield
An advisor on call for every vendor conversation

Always on advisory for renewals, audits and contract questions across your software vendors.

Explore Vendor Shield

enterprise software licensing news, once a week.

Price changes, audit activity and what worked in recent renewals. No vendor spin.