Negotiating EDP Service Exclusions and Carve Outs

Negotiating EDP service exclusions and carve outs

Negotiating EDP service exclusions and carve outs is where the real discount is won or lost, because the eligibility definition decides how much of your spend the discount actually touches. The Enterprise Discount Program applies its negotiated rate to eligible spend, and as of June 2026 certain categories are commonly carved out, including taxes, support charges, credits, and specific services, which still bill at full price and do nothing to satisfy your commitment (source: AWS EDP eligibility terms, as of June 2026). A headline discount on a narrow eligibility base is a smaller discount than it looks.

Sellers present exclusions as standard and fixed. Many are negotiable. The eligibility line is a commercial term, and pushing it in your favor before signature can recover more value than another point on the headline rate.

Find the carve outs before you agree the number

Read the addendum and list every category excluded from eligible spend. Then map your actual bill against that list to see how much of your spend the discount will never reach. If a large slice sits in excluded territory, two things follow: your effective discount is lower than the slide claims, and your commitment is harder to satisfy because excluded spend does not count toward it.

• Identify which services in your bill fall outside eligible spend.
• Quantify the excluded spend as a share of your total AWS cost.
• Recalculate the effective discount against the eligible base only.
• Flag categories where exclusion materially changes the deal economics.

Our walkthrough on Reading the AWS EDP addendum line by line, clause by clause shows exactly which clauses in the addendum govern eligibility, so you know where to look.

Marketplace inclusion is the big one

Marketplace inclusion is negotiable, and for many enterprises it is the single most valuable carve out to close. Third party software bought through AWS Marketplace can represent a large and growing share of cloud spend, and whether it counts toward your committed amount swings the math by millions. Push to include eligible Marketplace purchases in the committed spend, and confirm the treatment in writing rather than in conversation.

Including Marketplace spend does two things at once. It raises the share of your real spend that earns the discount, and it makes the commitment easier to reach, lowering shortfall risk. Both move value to your side of the table.

Support charges and the effective rate

Enterprise support is commonly priced as a percentage of usage, and whether it counts as eligible spend has an outsized effect on the math. If support sits outside eligible spend, a meaningful slice of your bill earns no discount and does nothing toward the commitment, while still being unavoidable. Raise support treatment explicitly, because it is rarely the first thing a seller volunteers and it can move the effective rate by a full point or more.

Where support cannot be made eligible, factor its cost into your view of the real discount. A headline rate that ignores a large support line is not the rate you actually pay, and comparing offers on the headline alone will mislead you.

Push the eligibility line, do not just accept it

Treat the exclusion list as an opening position. For each carve out, ask why it exists and whether it can move. Some exclusions are structural and will not change. Others are defaults the seller applies because most buyers never challenge them. The difference between those two is found only by asking, with leverage, before you sign.

Competitive tension helps. Holding Azure and GCP pricing reminds the provider that the spend in question is not guaranteed to stay on AWS. Timing the negotiation to the provider's quarter end adds pressure. The exclusions that look fixed in week one often soften in the final days of a quarter.

Sequencing the carve out negotiation

Negotiate exclusions in a deliberate order rather than all at once. Lead with the carve out that moves the most value, usually Marketplace inclusion, because winning it reshapes the whole deal economics. Then work through support treatment, service specific exclusions, and credits. Hold competitive tension throughout by keeping Azure and GCP pricing visible, and time the close to the provider's quarter end when flexibility peaks.

• Quantify each carve out as a dollar share of your bill first.
• Open with Marketplace inclusion, the highest value item.
• Trade smaller exclusions against commitment size or term where useful.
• Confirm every concession in the addendum, not in email or conversation.

A concession that is not written into the eligibility definition is not a concession. Get each one on paper before you treat it as won.

Measure the effective discount, then decide

The only discount that matters is the effective one: the negotiated rate applied to the spend that actually qualifies, net of the EDP stacking on top of Reserved Instances and Savings Plans. A generous headline on a narrow base can be worse than a modest headline on a broad base. Run the math both ways before you judge the offer, and use benchmarks to know what good looks like. Our guide on AWS EDP discount benchmarks by commitment size sets out the ranges.

Closing the carve outs also protects you from overcommitment, because more eligible spend means an easier path to the committed floor. Our companion guide on What to exclude from an AWS EDP commitment covers what you should deliberately keep out of the commitment, the mirror image of this work. This is commercial negotiation guidance, not legal advice; have your own counsel interpret the contract language.