AWS Marketplace EDP Commitment: What Counts
By Rostyslav Myronenko, AWS-certified solutions architect.
. 7 min read
How much of your AWS Marketplace spend counts toward an EDP commitment depends on three clauses in your addendum: the share of each Marketplace dollar that counts, the cap on how much of the annual commitment it can cover, and which products qualify. Get all three in writing before you sign: the public rules have changed twice since 2022, and your addendum overrides them.
This post covers the commitment mechanics only. What an EDP is, how the discount works and how to negotiate one are in the AWS EDP and PPA negotiation guide, and the two names are compared in AWS EDP vs PPA.
How Marketplace spend retires the commitment
An EDP, or the Private Pricing Addendum that papers it today, sets an amount you commit to spend on AWS each contract year. Software bought through AWS Marketplace is billed by AWS, so AWS lets some of it count toward that amount, under two rules.
Marketplace purchases count at the vendor's price and get no EDP discount (CloudForecast). A $100,000 SaaS contract retires $100,000 of commitment, if it qualifies, and you still pay the vendor $100,000. The discount in your addendum applies to eligible AWS services, and Marketplace spend sits outside it.
The share that counts has moved over time. Until 2022, 50 cents of every Marketplace dollar counted toward the commitment. At the start of 2022, new contracts began counting 100% of eligible Marketplace spend, capped at 25% of the annual commitment (Last Week in AWS, Duckbill). Neither rule is published by AWS, and the agreement you sign can say something else. The VTEX addendum filed with the SEC in 2024 counts "50% of fees for purchases on AWS Marketplace" as commitment-eligible fees, and it excludes taxes and anything paid from a shortfall balance.
The cap, worked through
Take a labelled example: a $1M annual commitment with the 2022-style terms, 100% of eligible Marketplace spend up to a 25% cap.
- The cap is $250,000 of commitment a year. Marketplace purchases beyond that still appear on the bill, but they retire nothing more.
- AWS usage has to cover at least $750,000 on its own. If it comes in at $700,000, a $300,000 Marketplace plan leaves a $50,000 shortfall, because only $250,000 of it counts.
- Under a 50% clause like VTEX's, the same $300,000 of software retires $150,000. The AWS usage then has to reach $850,000.
The cap is on commitment retired, so its value depends on how close your AWS usage already gets. A team whose eligible AWS spend runs above the commitment gets nothing from the Marketplace clause; a team forecasting a 10% shortfall can close it with software it was going to buy anyway. The how shortfall billing works section of the negotiation guide explains what happens when the year closes short.
Which products count
AWS decides eligibility product by product. Its Marketplace buyer guide says committed spend can be used for a product "if the products are eligible for AWS committed spend drawdown", that "products deployed on AWS typically qualify", and that eligibility "is determined separately for each product" (AWS Marketplace buyer guide).
"Deployed on AWS" has a definition. Since 1 May 2025 AWS Marketplace lists SaaS products wherever they are hosted, and marks the ones that run entirely on AWS with a Deployed on AWS badge on the product page (AWS What's New). To earn the badge, a product's application plane and control plane must both run on AWS, and so must any third-party service that transmits, stores or processes application data, with exceptions for content delivery networks, DNS and corporate identity providers. Agents and gateways may run in the buyer's environment as long as they send data only to AWS. Sellers prove it with an architecture diagram that AWS reviews and never publishes (AWS Marketplace SaaS guidelines).
AWS's own pages say badged products "may qualify for additional AWS customer benefits" without naming them. The guides that watch this market are more direct: Duckbill writes that from 1 May 2025 "only SaaS products hosted entirely on AWS will qualify for commitment retirement", that a migration product counts only if AWS is its only target, and that professional services fees don't count (Duckbill). CloudForecast adds that AWS told sellers about the change, not buyers, so a tool that counted in 2024 may not count now (CloudForecast).
So a vendor that hosts part of its stack on another cloud no longer helps you, however long you've bought it through Marketplace. The badge is a page element, so check each product page or ask your account team; PointFive notes that badge status isn't exposed through APIs or cost reports (PointFive).
Private offers and renewals
A private offer is how you buy Marketplace software at a negotiated price: the vendor and you agree a price and terms, the vendor creates the offer for your AWS account, and once you accept it the purchase "shows up like any other AWS Marketplace product in your monthly bill", with a line item for each kind of usage (AWS Marketplace buyer guide). A private offer changes only the price, so the product's eligibility still decides whether the spend counts.
Renewals work the same way. AWS's Marketplace blog says that "if a buyer has a spend commitment with AWS, eligible AWS Marketplace transactions can count toward it", and qualifying renewals "draw down against a customer's existing committed spend with AWS" (AWS Marketplace blog, September 2026). A multi-year private offer with an instalment schedule spreads those drawdowns over several contract years, so check which year each payment lands in before you count on it.
Where it shows in the bill
In the Cost and Usage Report, the bill/BillingEntity column separates the two kinds of charge: AWS for AWS services and AWS Marketplace for Marketplace purchases (CUR billing columns). The lineItem/LegalEntity column names the seller of record, which for third-party Marketplace products differs from the AWS entity that invoices you (CUR line item columns). Filter on the billing entity and group by product to see your Marketplace spend by vendor and by month.
The report won't tell you whether a line counts toward the commitment. The badge isn't in it, and because the EDP discount doesn't apply to Marketplace purchases, don't expect a discount line against those rows either. Keep your own list: vendor, product, badge status on the day you checked, and the share that counts under your addendum. AWS Marketplace's Single Pane of Glass dashboard shows the Deployed on AWS status per agreement and a table of committed future charges, which helps with the first two columns (AWS Marketplace blog, October 2025).
Planning Marketplace into the commitment
Before the negotiation, list the software you already pay for and find out which vendors sell on Marketplace with the badge. That list is worth money twice: it tells you how much of the commitment software can realistically cover, and it tells AWS you understand the clause.
Then negotiate the share and the cap. Both are lines in the addendum, and they belong in the same round as the discount and the exit terms. If your software spend is large, ask for a higher cap; if it's small, trade the clause for something you'll use.
Use the clause to close a gap you can see coming. In the negotiation guide's exit strategy section, bringing forward software you were going to buy anyway is one of the few mid-term levers you have. Software you wouldn't otherwise buy is a second commitment with the same problem as the first.
If you're not sure your spend is at the level where this matters, the AWS EDP eligibility checklist shows where you stand. The wider cost picture, including whether the AWS usage itself is as lean as it should be before you commit to it, is what the packages on my FinOps consulting page are for.
FAQ
Is AWS Marketplace spend discounted under an EDP?
No. Eligible Marketplace purchases retire the commitment at the price you agreed with the vendor, and the EDP percentage doesn't apply to them. The benefit is reaching the commitment with software you'd buy anyway; the price of that software doesn't change.
Do Marketplace private offers count toward an EDP commitment?
A private offer is a negotiated price for a Marketplace product, and the purchase appears on your AWS bill like any other Marketplace line. Whether it counts depends on the product: AWS decides eligibility product by product, and since 1 May 2025 a SaaS product qualifies only if it runs entirely on AWS. Ask the vendor and your account team before you sign.
What is the Marketplace cap in an AWS EDP?
The share of the annual commitment that Marketplace purchases can retire. Public guides describe contracts from 2022 on counting eligible purchases in full, up to 25% of the annual commitment, where earlier contracts counted 50 cents of each dollar. Your own cap is in your addendum: the VTEX addendum filed with the SEC in 2024 counts 50% of Marketplace fees.
Getting the Marketplace terms right before you sign
The Marketplace clause is a few lines in a long addendum, and it is easy to accept the default. If an offer is on the table, AWS EDP negotiation is where I model the commitment with your billing data, mark up the term sheet clause by clause, including this one, and prepare your team for each session with AWS.