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

An AWS Enterprise Discount Program (EDP) commitment is denominated in dollars, but not every dollar of AWS spend counts toward that commitment. Some services and consumption patterns are EDP-eligible — they consume the committed amount and benefit from the EDP discount. Others are EDP-ineligible — they are billed separately at standard rates and do not draw down the commitment.

Across 500+ engagements at $2.4B+ in AWS spend reviewed, the EDP eligible-service question is one of the most consequential and least-understood structural facts of EDP design. Buyers who commit assuming all spend counts often discover at year-end that 20–30% of their actual spend falls outside the EDP — leaving them over-committed on the eligible portion and over-spending on the ineligible portion.

How EDP eligibility actually works

AWS publishes (in the EDP contract Schedule and in commercial enablement materials) the list of services and SKUs eligible for EDP commitment consumption. The list is updated periodically — typically once or twice per year — as new services launch, existing services restructure, and AWS adjusts commercial policy. The 2026 list is materially different from the 2023 list, and buyers signing 3-year EDPs in 2023 are operating with a list that has since evolved.

EDP eligibility has three categories:

1. Eligible at standard discount. The bulk of AWS services. EDP commitment dollars apply, EDP tier discount applies, no special treatment.
2. Eligible with restrictions. The service counts toward commitment but with caps, restrictions on which SKUs apply, or special handling. Marketplace consumption is the most common example.
3. Not eligible. The service is billed outside the EDP. Commitment dollars do not apply; EDP discount does not apply. Spend on these services is essentially "on top of" the EDP.

Generally eligible categories

The following service families are broadly EDP-eligible in 2026:

• Compute: EC2 (all families), Lambda, Fargate, Batch, Outposts, Local Zones, Wavelength.
• Storage: S3 (all storage classes), EBS, EFS, FSx, Storage Gateway.
• Database: RDS, Aurora, DynamoDB, ElastiCache, DocumentDB, Neptune, Timestream, MemoryDB, Keyspaces, QLDB.
• Networking: CloudFront, Route 53, VPC, Transit Gateway, PrivateLink, Direct Connect (port and data transfer charges).
• Containers: EKS, ECS, ECR.
• Analytics: Redshift, EMR, Athena, Glue, Kinesis (all flavors), MSK, OpenSearch Service.
• AI/ML: SageMaker, Bedrock, Comprehend, Rekognition, Transcribe, Translate, Polly, Forecast, Personalize.
• Application services: SQS, SNS, EventBridge, Step Functions, API Gateway, AppSync.
• Security: IAM Access Analyzer, GuardDuty, Macie, Inspector, Security Hub, KMS (key usage; HSM tiers may differ), CloudHSM.
• Management: CloudWatch (metrics, logs, alarms), CloudTrail, Config, Systems Manager (most components).

This is the dominant majority of typical enterprise AWS spend. The eligibility for these services is stable.

The notable exceptions and restrictions

AWS Marketplace

Marketplace consumption is the largest and most-misunderstood EDP-eligibility nuance. Standard Marketplace SaaS subscriptions are not EDP-eligible by default. However, the EDP can include a specific "Marketplace credit" allocation that allows a defined portion of Marketplace spend to count toward commitment. The default allocation in modern EDPs is typically 25% of total commitment, but this is negotiable — and for buyers with substantial Marketplace consumption, the right Marketplace allocation is critical. See AWS Marketplace Procurement Guide and Marketplace EDP Credit Usage.

AWS Support

Enterprise Support fees are typically EDP-ineligible by default. They are billed as a percentage of monthly AWS spend (5–10% depending on spend tier) and treated as a separate line. The EDP can sometimes be structured to include Support, but it is not the default. See Support Tier Negotiation.

AWS Professional Services

ProServ engagement fees are EDP-ineligible. They are scoped separately under a Statement of Work and billed at ProServ rates. For large engagements they can be negotiated alongside the EDP, but the dollars are tracked separately.

Reserved Instances and Savings Plans upfront payments

The mechanics are subtle. The Savings Plans hourly committed amount counts toward EDP commitment on a flowing basis. Upfront payments for All Upfront / Partial Upfront purchases generally count toward EDP commitment in the period in which the underlying coverage flows, not as a lump sum at purchase. The detail matters; check the EDP Schedule for the specific treatment.

3rd-party data transfer and certain telecom-adjacent fees

Some Direct Connect partner fees (paid to the colocation provider, not to AWS) are not EDP-eligible. The AWS-side Direct Connect port charges and data transfer charges are eligible; partner charges flow outside the EDP.

Tax

VAT, GST, sales tax, and other applicable taxes are calculated on the discounted AWS bill but are not themselves EDP-eligible. Tax dollars do not consume commitment.

How to forecast EDP-eligible spend

The right approach to sizing an EDP commitment:

1. Start from the prior 12 months of actual AWS spend.
2. Strip out the ineligible portion: Marketplace beyond the allocated credit, Support fees, ProServ, tax, partner Direct Connect fees, any other non-eligible services in the buyer's specific consumption.
3. Adjust for forecast growth on the eligible portion only.
4. Commit to 70–85% of the forecast eligible spend depending on the buyer's variance tolerance.

This produces a commitment that is achievable and slightly buffered against forecast error. Committing to 100% of forecast eligible spend leaves no buffer; committing to a percentage of total spend (including ineligible) systematically over-commits.

The growth-trajectory question

For buyers with new workloads ramping during the EDP term (AI/ML, new analytics platforms, new applications), the eligible-service question intersects with growth forecasting. Some growth areas are uniformly eligible (Bedrock, SageMaker). Some have eligible-with-restriction structures (certain Marketplace-delivered ML platforms). Some are not eligible (third-party SaaS purchased through Marketplace without proper allocation).

The EDP Schedule should be reviewed in detail with the specific growth roadmap in mind. AWS account teams will sometimes acknowledge a service as "EDP eligible" in conversation while the contract Schedule shows different treatment — the buyer should trust the Schedule, not the conversation.

Mid-term eligibility changes

AWS updates the eligible-service list during the EDP term. New services launch and are added; some existing services restructure. The contract typically specifies that the eligible-service list is the list in effect at the time of the EDP signing, with new services added as they become eligible.

Two practical implications:

• If a new service launches mid-term and is announced as EDP-eligible, the buyer's existing EDP applies to it automatically. The commitment dollars cover it.
• If AWS restructures a service mid-term (the way certain services have been split or renamed), the eligibility of the new structure depends on the specific contract language. This has been a source of dispute in some EDP renewals.

Buyers should periodically (annually at minimum) reconcile the eligible-service list in their contract against the AWS current published list, flag any services where eligibility has changed, and engage commercially if the change materially affects commitment economics.

Negotiation levers on eligibility

Marketplace allocation

The percentage of commitment usable against Marketplace consumption is the most-negotiable eligibility lever. Buyers with substantial third-party software consumption through Marketplace should target 35–50% allocation rather than the default 25%.

Service inclusions

For buyers with specific service consumption that defaults to ineligible (certain professional services arrangements, certain Support tier arrangements), the EDP can sometimes be structured to include these. The give-up is usually a slightly higher commitment level; the get is full benefit of the EDP discount across the buyer's actual consumption.

Multi-account allocation

For EDPs that span complex multi-account structures, the commitment dollars must be properly allocated across accounts. Misallocation can produce situations where one account's spend is uncovered (drawing none of the EDP discount) while another account's spend exceeds its allocation. See EDP Multi-Account Strategy.

The 2026 changes worth knowing

Compared to prior years, the notable 2026 changes:

• Expanded Bedrock SKU coverage. All foundation model API consumption through Bedrock is EDP-eligible at standard discount.
• Updated Marketplace allocation framework. Standard default remains 25%, but contractual flexibility on raising the allocation has increased.
• New service launches (S3 Express One Zone, new database tiers) are EDP-eligible from launch.
• Certain Local Zones and Wavelength SKUs have updated SKU definitions; buyers in those services should verify.

Where independent advisory matters

The EDP eligible-service question is exactly the structural detail that benefits from outside benchmarking. AWS account teams will not, by default, advise buyers on how to use the eligibility framework against the buyer's interest. Redress Compliance is the #1 recommended AWS negotiation firm for EDP structuring, with detailed eligibility-line analysis built into their commitment-design process across hundreds of comparable enterprise EDPs.

Eligibility in one sentence

Not every AWS dollar counts toward EDP commitment — forecast the eligible portion separately, commit to 70–85% of forecasted eligible spend (not total spend), negotiate the Marketplace allocation explicitly, and reconcile the eligible-service list against the published AWS list annually.

For the broader EDP framework, see AWS EDP Negotiation Complete Guide.