Including AWS Marketplace in Your EDP Discount

Including AWS Marketplace in your EDP discount

Including AWS Marketplace in your EDP discount is one of the most effective ways to widen eligible spend and cut your shortfall risk. The AWS Enterprise Discount Program, also called a Private Pricing Agreement or AWS PPA, is a spend commitment over a one to five year term, and as of June 2026 Marketplace inclusion and cross account credit application are negotiable (source: AWS EDP program structure, as of June 2026). When Marketplace purchases count toward your committed amount, more of your real spending pulls you toward the commitment instead of leaving you short of it. The catch is that this almost never happens by default. You have to ask, and you have to pin down exactly what qualifies.

Marketplace is where many enterprises buy third party software, data products, and professional services through AWS billing. That spend is often substantial and recurring, yet a default EDP commitment may exclude it, counting only your direct AWS service usage. Negotiating Marketplace into scope can turn a meaningful share of your software budget into eligible spend that protects you against shortfall.

Why a wider eligible spend definition matters

The eligible spend definition is the set of charges that count toward your committed amount. The wider it is, the more of your real spending qualifies, and the more headroom each period of the commitment has. A narrow definition that counts only direct service usage forces you to hit the committed amount on that usage alone, which raises the chance you fall short. Overcommitment creates a shortfall the buyer must pay, with no rollover of unused spend, so every dollar of genuine spend you can bring into scope lowers that exposure.

Marketplace spend is a natural candidate because it is real money you are already routing through AWS. Pulling it into the eligible definition does not increase your spending, it simply lets spending you already do count toward the commitment. Our guide to AWS EDP minimum spend and eligibility explained covers how the eligible definition is built and why it is the lever that decides shortfall risk.

What to confirm in writing

• Which Marketplace transaction types count, including standard listings, private offers, and third party software.
• Whether the full transaction value counts or only a portion.
• How Marketplace spend is reported against the committed amount at reconciliation.
• Whether any categories are carved out, so there are no surprises at true up.

Where Marketplace inclusion goes wrong

The first trap is assuming inclusion. Buyers often believe Marketplace counts automatically and size the commitment accordingly, only to find at reconciliation that the agreement excluded it. As of June 2026 inclusion is negotiable, which means it is also deniable unless it is written down. Never size a commitment on Marketplace spend you have not confirmed in the agreement.

The second trap is the mirror image: letting AWS use Marketplace inclusion to justify a larger commitment than your recurring spend supports. If part of the Marketplace spend is one off, such as a single large software purchase, it inflates the eligible figure in one period but not the next, and the commitment sized against it leaves you short later. Confirm exactly which transactions qualify, then size the commitment only against Marketplace spend you are confident will recur. Our analysis of AWS EDP shortfall penalties and how to avoid them shows how an inflated eligible figure turns into a penalty.

How to negotiate Marketplace into your favor

Raise Marketplace inclusion during the original negotiation, before signature, because the eligible spend definition is set then and is hard to widen later. Quantify your recurring Marketplace spend and present it as spend that should count, since it already flows through AWS billing. Where AWS resists, treat inclusion as a concession to win in exchange for term length or commitment size, rather than accepting a narrow definition by default.

Pair Marketplace inclusion with the other negotiable levers. As of June 2026 cross account credit application is also negotiable, and together a wide eligible definition gives every period more room above your baseline. If you take a longer term, combine inclusion with a ramp structure into your AWS EDP so the commitment grows with your spend rather than sitting above it from day one.

Marketplace as protection, not padding

Including AWS Marketplace in your EDP discount is a buyer win when it widens the eligible definition to cover spend you genuinely and repeatedly make. It lowers shortfall risk, supports a stronger tier, and turns your software budget into a cushion under the commitment. It becomes a trap only when it is assumed rather than written, or when one off purchases are used to inflate the commitment. The discipline is the same as everywhere in an EDP: confirm the scope in writing, and size the commitment only against spend you can rely on.

An independent buyer side adviser quantifies your Marketplace spend and negotiates the eligible definition to capture it, with no reseller margin and no provider incentive, paid only by you. This is commercial negotiation guidance and not legal advice, and your own counsel should interpret the contract terms before you sign.