AWS retires three support plans on January 1, 2027, and the Enterprise Support definition inside your 5-year PPA is amendable by AWS at will, so a $3M/month account can absorb a $1.12M annual support line that never gets renegotiated
AWS collapsed paid support into three plans on December 2, 2025, killing Developer, Business and Enterprise On-Ramp effective January 1, 2027, and adding an unpriced Unified Operations tier starting at $50,000 per month. Your PPA forces you to carry Enterprise Support for the full term while support sits outside the 5 to 20 percent discount, so the only protection is grandfathering, rate-equivalence and no-worse-off language drafted before signature.
Prepared by Redress Compliance · September 2, 2026 · AWS advisory practice. EDP and PPA negotiations benchmarked 2024 to 2026.
Executive summary
The exposure is not tier death, it is redefinition: Enterprise Support survives, but its contents live in Service Terms AWS amends unilaterally, and at $3M monthly spend the legacy band schedule bills roughly $93,500 per month, or $1.12M per year, entirely outside your discount.
Sign a five-year PPA in 2026 and you have committed to a support product whose scope, inclusions and band schedule AWS can restate three times before your term ends.
AWS already ran the forced-migration playbook: Enterprise On-Ramp customers are auto-upgraded to Enterprise Support in periodic batches through 2026 with one month of email notice and no customer action required.
That is the precedent for how mid-term packaging changes land, and it tells you the notice period you must extend by contract to 180 days minimum.
AWS has conceded rate reductions from 10 percent to 5 to 7 percent for $10M-plus spend customers who ask during PPA renewals, which proves the band schedule is negotiable and that 30 to 50 percent of a typical $500K to $2M annual support bill is avoidable.
Support fee caps and TAM terms reliably attract senior commercial attention at $5M to $10M annual commit, so the ask must be made in the same cycle as the commit, not after.
Unified Operations has no published rate card above its $50,000 per month floor, which means there is no external anchor for a rate-equivalence test unless you build one into the addendum exhibit.
AWS will offer the migration as a value story (Security Incident Response now included, Countdown Premium and Incident Detection and Response bundled) and use that bundling to justify a floor that is 10x your current Enterprise minimum.
What actually changes on January 1, 2027, and where it lands in your contract
Strip out the announcement language and the December 2, 2025 restructure does two things to a buyer under a multi-year commitment.
First, it closed Developer and Business Support to new subscriptions the same day it was announced, and it sets January 1, 2027 as the hard discontinuation date for Developer, Business and Enterprise On-Ramp.
Second, and this is the part that matters to a $3M/month account, it leaves Enterprise Support standing as a name while changing what sits inside it and planting a bespoke-priced tier above it.
Your PPA addendum almost certainly refers to "AWS Enterprise Support" as a defined term and then points at Service Terms for the substance. AWS can amend Service Terms unilaterally.
That gap between the defined term you signed and the amendable document where the entitlements actually live is the entire exposure, and no amount of discount negotiation touches it.
AWS has already demonstrated the migration mechanic it will reuse: On-Ramp customers are being auto-upgraded to Enterprise Support in periodic batches through 2026 on one month's email notice, no customer action required, while Developer and Business customers must actively opt in.
Read that asymmetry as a statement of intent. Note also the GovCloud carve-out, where all three retiring plans remain available. Regional grandfathering is administratively possible, which destroys the "we cannot do exceptions" answer before AWS gives it.
| Plan | Minimum | Published bands | Bundled add-ons |
|---|---|---|---|
| Business Support+ | $29/month per account | 9% to $10K, 7% $10K to $80K, 5% $80K to $250K, 3% above $250K | Countdown Premium $10K per project/month, chargeable |
| Enterprise Support (legacy bands) | $5,000/month (was $15,000) | 10% to $150K, 7% $150K to $500K, 5% $500K to $1M, 3% above $1M | Security Incident Response now included; IDR at $7K or 2% minimum, chargeable |
| Unified Operations | Greater of $50,000/month or percentage, 90-day minimum | 10% to $1M, 6% $1M to $5M, 5% above $5M | Countdown Premium and IDR included at no cost |
| Retiring January 1, 2027 | Developer, Business, Enterprise On-Ramp | On-Ramp minimum was $5,500 | Remain available in GovCloud (US) |
The table shows the trap in the middle column. At $3M monthly spend the legacy Enterprise Support schedule produces roughly $93,500 per month, about $1.12M a year, and third-party renderings of the new Enterprise bands do not agree with each other above $1M.
That means the band schedule you are being asked to live under for five years is not reliably published anywhere. Demand it as a signed exhibit to the addendum, not a URL.
The second reading is Unified Operations. It has no rate card at all: AWS describes pricing as based on your specific requirements and workload complexity.
An unpriced tier above your mandatory tier, with the add-ons you currently pay for (Countdown Premium at $10K per project per month, Incident Detection and Response at $7K or 2% minimum) bundled in for free, is a migration funnel.
AWS does not need to raise your Enterprise Support rate to raise your support bill. It only needs to move capability you already depend on above the line you signed for.
Treat this the way you would treat any support policy incorporated by reference: the document you did not negotiate is the document that reprices you.
The interlock that removes your exit: mandatory Enterprise Support, priced outside the discount
Here is why the packaging change becomes a captive repricing event rather than a shopping decision.
AWS requires PPA and EDP customers to maintain Enterprise Support for the full duration of the agreement, so on a five-year term you have contracted away the one response any buyer would otherwise use: downgrade, or move support to a third party, or split it.
At the same moment, support fees sit on top of the 5 to 20 percent commitment discount rather than inside it. Your negotiated discount, whatever band you landed in, does nothing to the support line.
And because support bills as a percentage of consumption, the line escalates automatically with growth and carries no renegotiation trigger. Growth from $2M to $4M in monthly spend takes support from roughly $65,000 to roughly $125,000 a month without a single conversation.
Nobody signs off on that increase. It simply arrives.
Read the three facts together and the leverage picture is clear. Mandatory tier, plus outside-the-discount pricing, plus automatic escalation, plus a definition AWS can amend, equals a fee stream with no natural review point for the entire term.
That is precisely the structure a vendor builds when it expects to change the product mid-term.
The counter is not to fight the requirement, which AWS holds firm on, but to attack the price and the definition.
And the price is provably soft: in our benchmarking work we have seen AWS reduce Enterprise Support from 10 percent toward the 5 to 7 percent range for $10M-plus accounts that raise it at renewal.
Roll that into the same redline pass you use on the rest of the PPA, and price the ask in dollars: on a $3M monthly account, taking the blended effective rate down three points is worth well over $1M across a five-year term, which is real money against a $1.12M annual line.
Protect your AWS EDP commit with 6 flexibility clauses
Six flexibility clauses protect an AWS EDP commit: rollover, carryforward, over commit caps, under commit relief, and clean exit ramps.
Get the white paper →The three clauses to insert: grandfathering, rate-equivalence, no-worse-off
Three clauses, drafted as addendum exhibits rather than as email assurances, are what stand between you and a repriced support line in month 19 of a 60 month term. The mechanic you are defending against is not a tier sunset. Enterprise Support survives January 1, 2027.
What dies is Developer, Business and Enterprise On-Ramp, and what arrives above you is Unified Operations at a $50,000 per month floor with no published rate card.
The exposure is that "AWS Enterprise Support" in your PPA is a defined term whose substance sits in Service Terms AWS amends unilaterally. So the first clause pins the substance.
Attach the legacy Enterprise Support band schedule (10 percent on the first $150,000, 7 percent to $500,000, 5 percent to $1,000,000, 3 percent above) as a numbered exhibit.
And state that the exhibit controls over the Service Terms and any successor support plan documentation for the full term of the agreement, notwithstanding any incorporation-by-reference language elsewhere.
The reason this works: AWS has already conceded that carve-outs are administratively possible by keeping all three retired plans alive in GovCloud (US). You are asking for a contractual carve-out, not a technical impossibility.
The second clause converts marketing into representation.
AWS's own Premium Support FAQ says existing Business and Enterprise Support customers "will not see a cost increase." Paste that sentence into the addendum as an affirmative representation, then pin the numbers behind it: the $5,000 per month Enterprise minimum, the band percentages.
And an explicit statement that the effective support rate as a percentage of pre-discount AWS charges will not exceed the exhibit schedule in any billing month.
Rate-equivalence without a numeric anchor is unenforceable, and Unified Operations has no public anchor by design. The third clause is the no-worse-off test, and it is where the real value sits, because AWS's likely move is not a rate increase but an unbundling.
Any repackaging must preserve, at no incremental fee, the response time commitments, named TAM allocation, the 75 percent AI credit entitlement Enterprise carries today, and the included services as of the effective date, including AWS Security Incident Response.
Countdown Premium at $10,000 per project per month and Incident Detection and Response at the greater of $7,000 or 2 percent of enrolled account charges are the two line items AWS will use as the upsell wedge.
So name them and price them at zero if they later become bundled into any tier you are migrated to.
Cap the trigger at 180 days written notice and attach the remedy: if AWS breaches, your obligation to maintain Enterprise Support under the PPA terminates while every discount and credit survives. That last sentence is the whole clause. Everything before it is setup.
The remedy is the leverage, not the language.
A grandfathering clause with no consequence is a request; a grandfathering clause that releases you from the mandatory Enterprise Support obligation while preserving your discounts converts a $1.12M annual line at $3M monthly spend into something AWS has to protect to keep.
Once your support obligation is severable from your commit, AWS's ability to reprice support becomes a self-inflicted wound, and repackaging conversations start going your way without a call.
Sequence this alongside the broader AWS Private Pricing Agreement redlines rather than as a standalone support amendment, because a support carve-out negotiated after signature costs you the only lever you had.
Why AWS will concede the rate and fight the definition
Twenty five years across the table from vendors of this shape produces one reliable read: the number is negotiable and the definition is not, and the reason is organizational, not commercial. The support percentage is a variable a commercial lead already owns.
It sits in a discount approval matrix, it has documented precedent (AWS has moved Enterprise Support from 10 percent down to 5 to 7 percent for $10M plus spenders who asked at renewal), and conceding it costs the account team nothing they cannot recover through commit depth.
A rate concession is a signature. Grandfathering the contents of Enterprise Support is a product exception, and no one on your account team owns the product.
It requires someone in service leadership to agree that one customer's entitlement set is frozen while the portfolio moves, which is precisely the sovereignty AWS spends its contract architecture protecting.
That asymmetry tells you to invert the ask sequence most buyers use. The instinct is to open on rate because rate is quantifiable and feels like the win. It is the wrong order.
Open on definition while the commit is unsigned, because the definition ask is the one that has to travel outside the account team, and travel takes weeks you only have before signature.
Once the PPA is executed, your definition request has no carrier: there is no consideration left to trade, and the request becomes a support ticket. Rate comes second, and it comes cheaply, because by then you have established that you read Service Terms and you will not sign around them.
Buyers who lead with rate typically get 3 points off the top band and lose the entitlement set entirely, which is the expensive half of the trade.
Read the packaging moves as staging, not generosity.
Security Incident Response arriving in Enterprise Support at no additional cost, Countdown Premium priced at $10,000 per project per month for Business Support+ and Enterprise but included free with Unified Operations.
And Incident Detection and Response at the greater of $7,000 or 2 percent for Enterprise but bundled at the top tier: this is a value gradient built to make $50,000 per month look rational to a buyer already paying for three add-ons.
The Unified Operations bands (greater of $50,000 per month or 10 percent to $1M, 6 percent to $5M, 5 percent above) exist, but the User Guide says pricing is based on your specific requirements and workload complexity. The absence of a firm rate card above the floor is not an oversight.
It removes the benchmark you would otherwise use to run a rate-equivalence test, which is exactly why you have to build that benchmark yourself in the exhibit rather than expect to find one published.
Now the response pattern. When you hold the definition ask, three things happen in sequence. First, escalation: the ask leaves the account executive and goes to a specialist or a legal reviewer who explains, correctly, that Service Terms cannot be frozen as a matter of policy.
Treat that as an opening position, not a wall, because GovCloud already proves plan-level carve-outs are administrable. Second, a credit substitution: AWS offers a one-time support credit, often sized to look like 6 to 12 months of the delta, in place of the definition.
Credits are the vendor's preferred currency because they expire, they do not set precedent, and the offer composition shifts quarter to quarter, which means the credit you are shown in Q3 is not the structure you will be shown in Q4. Do not trade a permanent entitlement for an expiring balance.
Third, timing: the counter arrives close enough to your fiscal deadline that redlining it looks like a schedule risk. That is the tell that the ask is being taken seriously.
The strong outcome is specific.
Legacy Enterprise Support bands attached as a controlling exhibit for the full term, the current entitlement set including the 75 percent AI credit level frozen at no incremental fee, 180 days notice on any repackaging.
And a right to drop the mandatory support obligation on breach without touching the commit or the 5 to 20 percent discount.
If the definition genuinely will not move, price the risk instead: take the rate to 5 to 7 percent at the top band and shorten the term to three years so the repackaging lands at your renewal rather than mid-term.
A rate concession you can bank plus a shorter exposure window beats a longer, deeper discount wrapped around an entitlement AWS can rewrite.
This is the same failure mode Oracle's incorporation-by-reference clause has produced for two decades, and the defense has not changed: name the document, attach the version, and make the vendor buy any change.
What the evidence base shows about timing, notice and concession patterns
The pattern in AWS's own transition documentation is the tell. On-Ramp customers get moved to Enterprise Support during renewal or in periodic batches through 2026, with one month of email notice and no customer action required.
Developer and Business customers, by contrast, must actively opt in to the replacement plan.
That asymmetry is deliberate: where the migration raises the floor, AWS makes it passive and administrative; where it lowers revenue (Business Support+ starts at $29 per month against $100), AWS makes the customer come and ask.
Read that as the default posture you will face at your own mid-term repackaging event: an email, thirty days, and a billing change already in flight.
The second pattern is the missing exhibit. Legacy Enterprise Support bands are well established at 10 percent on the first $150,000, 7 percent to $500,000, 5 percent to $1,000,000 and 3 percent above that, which is how a $3M per month account arrives at roughly $93,500 monthly, $1.12M a year.
Third-party renderings of the new Enterprise band schedule conflict with the legacy one and simply stop above $1M.
AWS's public pricing page carries the minimums and the Business Support+ tiers but does not settle the top of the Enterprise curve.
And Unified Operations is openly bespoke: pricing "based on your specific requirements and workload complexity." You cannot build a no-worse-off test against a schedule nobody can produce.
That is precisely why the band table has to appear as a signed exhibit rather than a reference to a URL AWS controls, the same failure mode described in policies incorporated by reference.
$5M to $10M annual commit lands around 12 to 16 percent, $10M to $50M around 16 to 22 percent, and 20 percent is the practical ceiling.
AWS has reduced Enterprise Support from the 10 percent entry band to 5 to 7 percent for $10M-plus spenders who raise it during PPA renewal.
Three recurring behaviors follow from the deal file. First, support caps, blended rates and named TAM commitments only become genuinely negotiable at roughly $5M-plus annual commit; below that, the rep has no approval path and will not manufacture one.
Second, the 25 percent Marketplace contribution cap is a separate offset mechanism from the discount, so it buys you commit relief (on a $5M commit, up to $1.25M of qualifying Marketplace spend), not a cheaper support line. Do not accept it as the answer to a support ask.
Third, support protection travels with the shortfall cure and step-down asks: same paper, same signature window, same approver. Bundle them, because each one alone looks like a favor and all three together look like a deal.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Model support at end-of-term consumption, not today's run rate. At $3M monthly you are carrying roughly $1.12M a year; if consumption doubles across a five-year term, percentage billing drags support toward $2M annually with no renegotiation event, so put the year-five number in the business case before you discuss discount depth, and expect AWS to argue support is "self-correcting" because higher bands are cheaper.
- Demand the full Enterprise band schedule as a signed exhibit before commit sign-off. Ask for the bands above $1M in writing and hold the commitment signature until they arrive; AWS will point to the pricing page and the FAQ line that existing customers "will not see a cost increase," and a strong close is that sentence converted into a contract representation with the numeric table attached, not a link.
- Table the 5 to 7 percent blended rate alongside the commit tier, not after it. Precedent exists at $10M-plus spend, so price the concession as part of tier selection; AWS will counter with value adds already bundled (Security Incident Response at no cost, higher AI credit entitlements) and a strong outcome is a blended rate at or below 7 percent with an annual dollar cap, worth $300,000 to $400,000 a year on a $1.12M line.
- Push notice from 30 days to 180, with a release remedy attached. The On-Ramp precedent is one month of email; ask for 180 days written notice of any change to the definition or pricing of your support plan, plus the right to be released from the mandatory Enterprise Support obligation if the change raises effective cost by more than 5 percent. AWS resists release rights hardest, so a defensible landing is 120 days plus a fixed-rate election, and the wider clause set is mapped in the PPA redline library.
- Set a contractual mid-term review milestone dated to January 1, 2027. Write a joint pricing review triggered at the packaging change, with your commit and support rate both in scope and a documented step-down or reallocation right if the new packaging removes entitlements you paid for; AWS will call it a renegotiation opener and try to make it a "business review," so insist the clause names the remedies rather than the meeting.
Frequently asked questions
Is AWS Enterprise Support being discontinued in 2027?
No. Enterprise Support survives the restructure. Developer Support, Business Support and Enterprise On-Ramp are the three plans discontinued on January 1, 2027, and all three closed to new subscriptions on December 2, 2025.
The risk to Enterprise Support customers is repackaging and repricing of what the plan contains, not removal of the plan itself.
Can AWS change my support plan mid-term if I signed a five-year PPA?
Yes, unless you drafted against it. Your PPA addendum references AWS Enterprise Support as a defined term, but the substance of that term lives in Service Terms that AWS amends unilaterally.
The Enterprise On-Ramp migration is the working precedent: affected customers were auto-upgraded in batches with one month of email notice and no action required on their part.
What does Enterprise Support actually cost at scale?
Under the legacy band schedule (10 percent on the first $150,000, 7 percent to $500,000, 5 percent to $1M, 3 percent above), a customer at $3M monthly AWS spend pays roughly $93,500 per month, or about $1.12M per year.
That charge sits on top of your negotiated discount, not inside it, so it is not reduced by a 16 percent PPA discount.
Will AWS negotiate the Enterprise Support percentage?
It has. Documented concessions take $10M-plus spend customers from 10 percent down to 5 to 7 percent when the ask is made during a PPA renewal.
Support fee caps and TAM terms generally become negotiable once annual commit reaches the $5M to $10M range, where deals attract senior commercial attention. The ask has to ride with the commit, not follow it.
What is AWS Unified Operations and do I need it?
It is the new top tier, priced at the greater of $50,000 per month or 10 percent up to $1M of monthly charges, with a 90-day minimum commitment. AWS does not publish a rate card for it above the floor, stating pricing depends on requirements and workload complexity.
Because it bundles Countdown Premium and Incident Detection and Response, AWS will present it as a value upgrade rather than a price increase.
Does the 25 percent Marketplace contribution reduce my support bill?
No. The Marketplace contribution cap lets qualifying Marketplace purchases count toward your annual commit, up to 25 percent of it, so on a $5M commit up to $1.25M can be satisfied that way.
It is a commit-attainment mechanism, entirely separate from the discount and from support fees, which are billed on top of everything.
What notice period should I demand for support packaging changes?
Thirty days is the AWS working default and it is not defensible.
Push for 180 days written notice of any change to plan contents, response commitments, TAM allocation or band schedule, paired with a remedy: if the change is material.
You are released from the obligation to maintain Enterprise Support for the remainder of the PPA term without triggering a discount forfeiture.
