What to Exclude From an AWS EDP Commitment

Deciding what to exclude from an AWS EDP commitment

What to exclude from an AWS EDP commitment is a question about risk, not generosity. The committed amount is a floor you must reach or pay a shortfall against, so every dollar you build into it should be spend you are highly confident will recur for the full term. As of June 2026, the AWS Enterprise Discount Program is a multi year spend commitment with no rollover of unused spend, so an overstated commitment is a direct liability (source: AWS EDP terms, as of June 2026). The discipline is to commit the durable base and leave the volatile, temporary, and non eligible spend outside the number.

Sellers prefer the opposite. A larger commitment looks like a larger discount and a larger booking. Your job, and ours on your behalf, is to separate the spend that genuinely belongs in the floor from the spend that should sit above it, earning the discount when it appears but never creating an obligation if it does not.

Exclude volatile and project based spend

Burst workloads, one time migrations, seasonal peaks, and project based compute do not belong in the committed floor. They inflate the baseline in the year you measure them and then vanish, leaving you committed to a level you cannot sustain. Model your spend as a durable base plus a variable layer, and commit only the base.

• Short lived migration spend that ends once the project completes.
• Seasonal or campaign driven peaks that do not recur evenly.
• Proof of concept and experimentation environments.
• Workloads with a known end of life inside the term.

Forecasting this base accurately is the foundation of right sizing the commitment. Our guide on Forecasting spend before signing an AWS EDP walks through how to build a defensible forecast from real consumption.

Exclude spend that may move off the platform

If a workload is a candidate to move to another provider, to on premises, or to be retired, it should not anchor a multi year commitment. Multi year lock in removes future leverage, and committing spend you might migrate hands the provider an obligation you may not want to honor. Keep optionality by leaving migration candidates above the committed line.

This is also where competing quotes matter. Holding Azure and GCP pricing during the negotiation strengthens your position on the durable base and reminds the provider that not all of your spend is captive.

Exclude spend tied to uncertain business cases

Some spend exists only because a business case is still being proven. A new product line, a data platform under evaluation, or a workload whose owner has not yet committed internally should not anchor a multi year obligation. If the business case fails, the spend disappears, but your commitment does not. Keep that spend above the floor, where it earns the discount if it materializes and costs you nothing if it does not.

The same logic applies to spend that depends on a single large customer or contract. Concentrated, contingent spend is exactly the kind of usage that looks solid until the day it is not. Commit the diversified, durable base and let the contingent layer ride above it.

Watch the services the agreement already excludes

Separate from what you choose to leave out, the agreement itself excludes certain spend from eligibility. Taxes, support charges, credits, and specific services are commonly carved out, which means they do not count toward the commitment and still bill at list. Marketplace inclusion is negotiable, so whether third party Marketplace purchases count is a point to settle in writing.

Read the eligibility definition carefully and map your bill against it. If a large category is excluded by the agreement, do not assume it helps you reach the number. Our companion guide on Negotiating EDP service exclusions and carve outs covers how to negotiate these definitions so more of your real spend qualifies.

Size the commitment to the durable base

Once you have stripped out the volatile, the temporary, the migratable, and the non eligible, what remains is your durable eligible base. That is the number to commit, and even then a prudent buyer commits slightly below it to leave headroom. Overcommitment is the most common mistake in this program, and the cause is almost always a commitment sized to peak or forecast rather than to the floor.

The upside above the floor is still yours. Spend that exceeds the commitment earns the negotiated discount as it appears, with no obligation if it does not. You capture the discount on growth without carrying the risk of a forecast that never arrives. Our analysis of Why AWS EDP overcommitment is the most common mistake shows the shortfall cost of getting this wrong. This is commercial guidance, not legal advice; your counsel should review the contract terms.