An AWS EDP is a committed-spend agreement in which a customer promises AWS a level of spend over a term in exchange for discounts — and because eligible AWS Marketplace purchases draw it down, it quietly shapes how your enterprise buyers prefer to buy.
When an enterprise prospect asks “can we put this on our AWS bill?”, there’s usually an EDP behind the question. Most sellers hear a procurement preference. What’s actually driving it is a budget the customer has already committed to spend.
The EDP is a buyer-side agreement — you aren’t a party to it — but it changes the economics of every deal you run with that customer. Purchases that draw down the commitment are, in effect, money the buyer has to spend anyway.
Here’s what an EDP is, how marketplace purchases interact with it, and what it means for the way you sell.
What is an AWS EDP?
An AWS EDP (Enterprise Discount Program) is a private, negotiated agreement between AWS and a customer in which the customer commits to spend a minimum amount on AWS over a multi-year term, and AWS provides discounts in return. It’s a buyer-side contract — the discount rewards the customer’s committed spend, and it scales with the size of the commitment.
From the buyer’s side, the point of an EDP is predictable pricing at scale. A company running large workloads on AWS trades some flexibility for a better rate: they promise a spend floor, and AWS discounts against it.
As a software seller, you are not a party to the EDP. But you sell to companies that have one, and that changes what they want from you.
How do AWS Marketplace purchases draw down an EDP?
Eligible AWS Marketplace purchases count toward a customer’s EDP commitment. When a customer buys your software through AWS Marketplace, that spend generally applies to the amount they’ve already committed to spend with AWS.
That’s the mechanic that matters. A third-party software purchase made through the marketplace isn’t separate from the customer’s AWS relationship — it flows through it. So the dollars a buyer spends on your product can do double duty: they buy your software and they retire part of a commitment the buyer has to meet regardless.
Buying the same software outside the marketplace — a direct contract, a separate invoice — does none of that. The spend sits outside the EDP, and the commitment still has to be met some other way.
Why does an EDP make marketplace the preferred buying path?
For a customer with an EDP, buying through the marketplace turns a cost into progress toward an obligation they’ve already signed up for. Every eligible dollar spent in the marketplace is a dollar they don’t have to find elsewhere to hit their commitment — which is why procurement teams at EDP accounts often steer purchases onto the marketplace by default.
This is the part sellers underestimate. When an enterprise buyer asks to transact on AWS Marketplace, it’s frequently not a preference — it’s direction from finance to route spend through the committed channel. A vendor who can’t sell that way creates friction against the buyer’s own budget structure.
The implication: marketplace eligibility isn’t a billing detail. For EDP accounts, it can be the difference between an easy yes and a procurement escalation.
What does an EDP mean for you as a seller?
It means you should make your software easy to buy the way EDP customers want to buy — through the marketplace, on terms that fit an enterprise deal. Two moves do most of the work.
First, be marketplace-eligible: list and sell on AWS Marketplace so an EDP customer can transact with you through the channel that draws down their commitment. If you’re new to the mechanics, start with AWS Marketplace for sellers.
Second, use private offers for anything beyond a standard public price. Enterprise deals rarely close at list — they close at a negotiated price, a custom term and a payment schedule. Private offers on the marketplace let you deliver that negotiated deal through the marketplace, so it still counts toward the buyer’s EDP while matching the commercial terms you agreed.
Put together: the buyer gets EDP drawdown and a negotiated price, and you get a closed deal instead of a procurement standoff.
How does an EDP compare to Azure and Google Cloud?
Every major cloud has a committed-spend program, and each counts eligible marketplace purchases toward the commitment. The names differ; the mechanic is the same.
| Cloud | Committed-spend program | Marketplace draws it down? |
|---|---|---|
| AWS | Enterprise Discount Program (EDP) | Yes |
| Microsoft Azure | Microsoft Azure Consumption Commitment (MACC) | Yes |
| Google Cloud | Committed-spend / consumption agreements | Yes |
The takeaway holds across all three hyperscalers: enterprise buyers with a commitment prefer to buy software through the marketplace that draws it down. For the Microsoft side, we cover the Azure equivalent, a MACC in depth.
What do sellers get wrong about EDPs?
The most common mistake is treating an EDP as purely the buyer’s problem. It shapes your deal whether or not you engage with it, so ignoring it just means being surprised by it. A few others are worth clearing up:
- “An EDP discounts my software.” No. The discount applies to the customer’s AWS spend, not your price. Your pricing stays yours to set.
- “The customer needs a massive AWS footprint.” EDPs do skew toward larger accounts with meaningful multi-year commitments, but the drawdown mechanic — marketplace spend counting toward the commitment — matters to any buyer who already has one, not only the very largest.
- “Marketplace takes a cut, so it’s worse for me.” The listing fee is usually outweighed by faster enterprise deals and access to committed budget — especially on private offers.
Frequently asked questions
What is an AWS EDP? An AWS Enterprise Discount Program (EDP) is a negotiated agreement where a customer commits to a minimum level of AWS spend over a multi-year term in exchange for discounts. It’s a buyer-side contract between AWS and the customer.
Do AWS Marketplace purchases count toward an EDP? Yes. Eligible AWS Marketplace purchases generally draw down a customer’s EDP commitment, which is why enterprise buyers with an EDP often prefer to buy third-party software through the marketplace rather than on a direct contract.
Does an EDP give me a discount as a seller? No. An EDP discounts the customer’s AWS spend, not your software price. You set your own pricing. Private offers let you deliver a negotiated price through the marketplace while the purchase still draws down the buyer’s commitment.
Should I list on AWS Marketplace because of EDPs? If you sell to enterprises, yes. Marketplace eligibility lets EDP customers apply their purchase to committed spend they have to meet anyway — often turning a procurement debate into a straightforward approval.
Do Azure and Google Cloud have an EDP equivalent? Yes. Azure has the Microsoft Azure Consumption Commitment (MACC) and Google Cloud has committed-spend agreements. Both count eligible marketplace purchases toward the commitment, the same way an AWS EDP does.
Takeaways
- An EDP is a buyer-side commitment between AWS and a customer — you’re not a party to it, but it shapes every deal you run with that customer.
- Eligible AWS Marketplace purchases draw down the commitment, which is why EDP customers prefer to buy software through the marketplace.
- Be marketplace-eligible and use private offers, so an enterprise buyer gets EDP drawdown and a negotiated price in one transaction.
- The pattern repeats on Azure and Google Cloud — committed spend plus marketplace drawdown is now the default enterprise buying path.
Suger helps software companies list, price and sell through AWS Marketplace, so EDP customers can buy your product the way their budget wants them to. See how it works on the Suger AWS Marketplace page.
Stay Updated
Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.