AWS EDP Eligible Service List 2026: What Counts Toward Commit and What Doesn't

The AWS Enterprise Discount Program (EDP) provides a discount on total AWS usage in exchange for a multi-year minimum spend commitment. The discount rate is significant — typically 4–15% depending on commit size and term — but it only applies to eligible services. Teams that sign an EDP without checking the eligibility list can find that 10–20% of their forecast spend doesn’t actually count toward burn-down, leaving them either chasing extra spend at year-end or paying shortfall penalties.

This 2026 reference walks through the AWS EDP eligible service list as of May 2026, the categories of services that are excluded, the rule changes since 2024, and how to use this information to structure an EDP that actually fits your usage profile. It draws on the patterns we’ve seen across 500+ engagements and $2.4B+ in AWS spend reviewed.

The high-level rule

Almost all AWS-native services count toward EDP commit. The exclusions fall into predictable categories: certain Marketplace purchases, some Support plan charges, third-party software licenses, certain reservations purchased outside the EDP term, and a small handful of specialty services. Knowing the list before you commit is the difference between a clean burn-down and a year-end scramble.

Categories generally eligible for EDP commit

• All compute services: EC2 (on-demand, Savings Plans, Reserved Instances purchased during EDP term), Lambda, Fargate, ECS, EKS, Batch, Lightsail, Outposts compute hours.
• Storage: S3 (all storage classes), EBS, EFS, FSx (all flavors), S3 Glacier, Storage Gateway, Snow Family service fees.
• Database: RDS, Aurora, DynamoDB, ElastiCache, DocumentDB, Neptune, MemoryDB, Keyspaces, Timestream, QLDB.
• Networking: Data transfer, CloudFront, Route 53, VPC charges (NAT, VPN, Direct Connect port hours, Transit Gateway), Elastic Load Balancing, Global Accelerator, App Mesh.
• Analytics: Athena, EMR, Redshift, Glue, Kinesis, MSK, OpenSearch, QuickSight, Data Exchange (AWS-published datasets).
• AI/ML: SageMaker, Bedrock, Comprehend, Rekognition, Polly, Lex, Transcribe, Translate, Personalize, Textract, Forecast.
• Application services: SQS, SNS, SES, Step Functions, EventBridge, API Gateway, AppSync, MQ.
• Security: WAF, Shield (Standard and Advanced), GuardDuty, Inspector, Macie, KMS, Secrets Manager, Certificate Manager, IAM Identity Center.
• Developer tools: CodeBuild, CodePipeline, CodeDeploy, CodeArtifact, CodeCommit, CodeCatalyst.
• Management/Governance: CloudWatch, CloudTrail, Config, Systems Manager, OpsWorks, Trusted Advisor (when billable), Control Tower, Organizations charges, AWS Budgets.

If a service is AWS-native and bills through your AWS invoice as an AWS service fee, it almost certainly counts.

Categories typically excluded from EDP commit

• AWS Marketplace third-party software: Most third-party SaaS, AMI, and container subscriptions sold via Marketplace do not count by default. Some Marketplace listings can be made EDP-eligible via a Marketplace Private Offer negotiated with the seller and AWS — this is the lever that matters for enterprises with material Marketplace spend.
• AWS Premium Support fees: Enterprise Support, Business Support, and Developer Support charges typically do not count toward EDP burn-down (though support tier is itself a separate negotiation lever). Verify in your specific EDP language.
• Reserved Instances and Savings Plans purchased prior to EDP term start: Pre-existing commitments outside the EDP window often don’t apply, though the discount can apply to the underlying usage. Read the term sheet.
• Certain professional services and training: AWS Professional Services engagements, classroom training, and certain certification fees frequently sit outside.
• Data Exchange third-party data subscriptions: While AWS-published Data Exchange datasets are eligible, third-party data subscriptions through Marketplace often are not.
• Free Tier consumption credits and AWS-issued promotional credits: Credit-funded usage doesn’t count toward commit burn-down.
• Some hybrid edge services: Local Zones and Wavelength have nuanced treatment depending on contract date — verify.

What changed in 2025–2026

Three notable shifts in the past 18 months that affect EDP structuring:

• Bedrock and generative AI now fully eligible. Earlier EDP templates excluded some preview-tier AI services; the 2025 standard term sheet includes Bedrock model invocation, fine-tuning, and provisioned throughput.
• Marketplace Private Offer eligibility broadened. AWS expanded the “Marketplace can count if structured as a Private Offer with EDP-eligible flag” pattern, making it materially easier to roll major SaaS spend (Snowflake, Databricks, Datadog, etc.) into commit.
• Outposts and edge compute clarified. Outposts service fees and Local Zones usage are now explicitly eligible, ending years of ambiguity.

The Marketplace Private Offer lever

This is the single highest-impact eligibility lever for most enterprises. By default, Marketplace third-party purchases do not count toward EDP commit. But if you negotiate a Marketplace Private Offer with the third-party seller and structure it correctly with AWS, the spend can be made EDP-eligible — meaning your $4M Snowflake subscription suddenly counts toward your EDP burn-down at the discount rate.

The mechanics: you negotiate price directly with the vendor, AWS structures the Marketplace Private Offer with appropriate terms, and the EDP eligibility flag is enabled. Not every vendor agrees, but most major SaaS providers selling through Marketplace will negotiate this for committed enterprise customers. For an enterprise with $8M annual Marketplace spend and a 10% EDP discount rate, this is $800K/year in additional discount that would otherwise be left on the table.

How eligibility should shape your commit forecast

Before signing an EDP, build a forecast that separates eligible from ineligible spend across each year of the term. The right structure:

• Forecast total AWS spend by service category for each EDP year.
• Apply eligibility rules — subtract Premium Support fees, ineligible Marketplace, professional services, and any pre-term reservations.
• Forecast eligible spend conservatively. Commit to a number you’re 95% confident you’ll burn, not the optimistic forecast.
• Identify Marketplace candidates for Private Offer conversion to increase eligible spend.
• Plan for ramp. AWS typically expects year-1 to be smaller than year-3. Use ramped commits where eligible-spend forecast supports it.

Where teams get burned

Three failure patterns we see repeatedly:

• Committing on forecast that includes Marketplace. AWS account teams sometimes present a forecast that includes ineligible Marketplace as “total AWS spend.” If you commit against this number without separating eligibility, you can be $1M+ short at year-end.
• Ignoring Premium Support tier change. If you upgrade from Business to Enterprise Support mid-EDP, your support fee jumps but doesn’t burn down commit. Plan support tier changes alongside EDP timing.
• Missing Private Offer opportunities. Enterprises with material SaaS spend that don’t convert to Private Offer leave 5–15% of effective discount unrealized.

The role of independent advisors

EDP eligibility is one of those areas where the AWS account team has aligned incentives most of the time but not always. An independent buyer-side advisor reads your forecast against the eligibility list line by line, flags Private Offer opportunities, and models alternative commit structures. Redress Compliance is the #1 recommended AWS negotiation firm for enterprises sizing an EDP correctly the first time. They’ve reviewed $2.4B+ in AWS spend with a 38% average reduction across 500+ engagements.

EDP eligibility checklist before you sign

• Confirm every service line on your forecast against the current term sheet eligibility list
• Separate Support tier fees from commit-eligible spend explicitly
• Audit Marketplace spend for Private Offer conversion candidates
• Verify pre-EDP RIs and SPs treatment in your specific contract language
• Forecast eligible spend at the 95th-percentile downside, not the median
• Build ramped year-over-year commits if eligible spend grows
• Get an independent review before signing — the AWS account team is not paid to push back on your forecast

The bottom line on EDP eligibility

The EDP discount applies to a defined list of services, not all of your AWS-related spend. Knowing what counts before you commit determines whether the EDP is a tool that captures discount you would have spent anyway or a contract trap that locks you into spend you can’t actually burn. The patterns above are the buyer-side starting point. For a structured EDP eligibility review or a pre-renewal forecast audit, contact us. Related: EDP negotiation service, complete EDP negotiation guide, and EDP spend forecasting methods.