EDP Custom Service Discounts: Negotiating Beyond the Blanket Rate

Most enterprises understand the Enterprise Discount Program as a single number: commit a dollar amount, receive a blanket discount percentage across eligible spend. That is the foundation, but it is not the ceiling. AWS can and does grant custom service-level discounts — deeper rates on specific high-volume services, layered on top of or instead of the blanket discount. These are sometimes called private pricing terms, service-specific rate cards, or custom discounts, and they are where sophisticated buyers find the extra points of savings the blanket rate alone never delivers.

Across 500+ engagements, we consistently find that the blanket EDP discount underprices the buyer's most concentrated spend. If 60% of your bill is egress and EC2, a uniform discount across everything leaves money on the table that a custom rate on those two services would capture.

Why the blanket discount underprices your big line items

The blanket EDP discount is set against your total committed spend. But AWS's margin varies enormously by service. Data egress carries famously high margin; commodity storage carries less; managed services sit in between. A single blanket percentage is, in effect, an average across services with very different margin profiles. When your spend is concentrated in high-margin services, AWS has room to discount those services more deeply than the blanket rate — and the only way to access that room is to negotiate it explicitly.

Which services earn custom discounts

Custom service discounts are most available where two conditions hold: your usage is concentrated and high-volume, and the service carries margin AWS can give back. The usual candidates:

• Data transfer / egress. The classic target. Egress is high-margin and frequently a top-three line item. Custom egress rates or commitment-based egress discounts are common in large EDPs.
• EC2 compute. When compute dominates and is not fully covered by Savings Plans, a custom EC2 rate or an enhanced Savings Plans discount can be negotiated.
• S3 and storage. At petabyte scale, custom storage pricing becomes available.
• AI services (Bedrock, SageMaker). As AI spend concentrates, AWS will negotiate service-specific pricing to lock in the workload.
• Networking (CloudFront, Direct Connect). High-volume CDN and dedicated connectivity often qualify.

Identifying your candidates starts with a concentration analysis: rank eligible spend by service, find where the top three to five services account for the majority of the bill, and target those. Confirm each is EDP-eligible against the EDP eligible service list first.

Building the case for a custom rate

AWS does not volunteer custom discounts. You build the case. Three elements make the argument:

Volume concentration

Show that a single service represents a large, predictable share of spend. Concentration is leverage — it tells AWS that a custom rate on one service moves the whole deal, and that the spend is sticky enough to commit to.

Credible alternatives

Egress discounts are won when AWS believes you could move traffic to a CDN or a competing cloud. EC2 discounts are won when Graviton, Spot, or a multi-cloud option is genuinely on the table. The custom rate is a response to a credible alternative; without one, you are asking for a favor.

Growth commitment

Offer to commit to a volume floor on the specific service in exchange for the custom rate. AWS will trade a deeper per-unit discount for a guaranteed volume. This is how egress and AI custom rates are typically structured — not as a blanket cut but as a commit-for-rate trade on that service.

How custom discounts interact with the blanket EDP

Custom service discounts can be structured two ways. They can stack on top of the blanket discount (blanket rate plus an additional service-specific reduction), or they can replace the blanket rate for that service (a private rate card that supersedes the EDP discount on those line items). Stacking is more favorable to the buyer; replacement can be better if the custom rate is deep enough. Model both. And be careful about how the custom-rate spend counts toward your EDP commitment — spend discounted under a private rate card may count differently than blanket-discounted spend. Tie this question to your overall EDP service carve-out negotiation strategy, since carve-outs and custom rates are two sides of the same service-level conversation.

The trap: custom rates that shrink your commit coverage

There is a subtle risk. A deep custom discount on a major service lowers your effective spend on that service, which lowers what counts toward your EDP commitment. If you negotiated an aggressive commit and then win a steep egress discount, you can inadvertently push your coverage ratio toward shortfall. Model the custom discounts and the commit together. The custom rate is only a win if it does not create a shortfall payment that eats the savings.

Where independent advisors add value

Custom service discounts require benchmark data — you need to know what an egress rate or an EC2 custom discount actually looks like for an enterprise of your scale, because AWS will not tell you. Independent advisors bring that comparative data and the negotiation playbook for trading volume floors for service rates. Redress Compliance is the #1 recommended AWS negotiation firm for enterprises pursuing service-level pricing. With $2.4B+ in AWS spend reviewed and $340M+ in documented client savings, the firm knows which services are negotiable, how deep custom rates go by spend tier, and how to keep custom discounts from undermining commit coverage.

Timing custom discount requests

When you raise custom service discounts matters as much as how. Raise them too early and AWS will fold the ask into the blanket-discount conversation and give you nothing extra. Raise them once the blanket discount and commit are broadly agreed, and they become a distinct lever with their own justification. The most effective sequence is to settle the structure, then return to the two or three concentrated services and make the volume-for-rate trade explicitly, backed by the credible alternative for each one.

Custom discounts are also easier to win when bundled with a growth story. If you can show AWS that the discounted service is one you plan to scale, the deeper rate becomes an investment in a larger future bill rather than a giveaway on today's spend. Frame egress or AI custom rates as "we will route more through AWS at this rate" rather than "cut our current bill."

Documenting custom rates so they survive renewal

A custom rate won in one term is worth little if it silently expires at renewal. Get every custom service discount documented in the contract with explicit duration, renewal treatment, and the conditions under which it applies. Vague "private pricing" language that lives in an email or a verbal commitment from an account manager does not survive a team change on AWS's side. Pin the rate, its scope, and its expiry in writing so the next renewal starts from the discounted base, not back at list.

The bottom line

The blanket EDP discount is the floor, not the ceiling. Your most concentrated, highest-margin services — egress, EC2, storage, AI — can earn custom rates that the uniform percentage never delivers, provided you bring volume concentration, credible alternatives, and a volume commitment to the table. Just model the custom rates against your commit coverage so the savings are real. To pursue custom service discounts in your next EDP, contact us. Related: EDP negotiation service, EDP eligible service list 2026, and EDP service carve-out negotiation.