AWS Pricing Model Explained: From Rate Card to Effective Rate
AWS pricing looks simple from the rate card — and then collides with EDP, Savings Plans, RIs, PPA, Marketplace, and discounts layered on discounts. Here is how the actual price you pay is built up, layer by layer.
AWS publishes rate cards for every service on a public pricing page. Enterprises rarely pay rate card. The price actually billed is the result of multiple programs stacking on top of one another — and understanding how those programs compose is the difference between sizing a $50M contract correctly and overpaying by $10-15M across the term.
This guide explains the AWS pricing model end-to-end. We will cover on-demand pricing, Reserved Instances, Savings Plans, Spot, EDP, PPA, Marketplace, support tier, and the way these layers combine into the effective rate that shows up on your invoice. By the end, you will be able to read an AWS proposal and decompose it into the levers that actually moved.
Layer 1: On-demand rate card
On-demand is the published price for using an AWS service without any commitment. It is the "list price" of cloud — and like list price in most B2B contexts, very few enterprises pay it on net. On-demand pricing has three traits worth understanding:
- It is the baseline for all other pricing. Every discount program is computed against on-demand rates. A "40% discount" means 40% off the on-demand rate at the time you are billed.
- It changes. AWS adjusts on-demand rates over time — usually downward for established services, occasionally upward for niche services or to align pricing across regions. Your contract may or may not pin you to a specific on-demand baseline.
- It varies by region and by service. US-East-1 is the cheapest region; EU and APAC regions are 10-25% more expensive on most services. Inter-region transfer is its own complex pricing line.
Layer 2: Reserved Instances
Reserved Instances (RIs) are AWS's original commitment-discount program. You commit to using a specific instance type in a specific region for a one- or three-year term, in exchange for a discount versus on-demand. RIs come in three payment options:
- No Upfront: Smallest discount (~36% for three-year), monthly billing
- Partial Upfront: Mid-tier discount (~42% for three-year), partial upfront payment
- All Upfront: Largest discount (~52% for three-year), full upfront payment
RIs are still relevant for specific services — RDS, ElastiCache, OpenSearch, Redshift, DynamoDB Reserved Capacity, and some niche EC2 workloads. For most general-purpose EC2, Savings Plans have largely superseded RIs.
Layer 3: Savings Plans
Savings Plans are AWS's newer commitment-discount program (launched 2019). You commit to a dollar-per-hour spend on compute for one or three years, in exchange for a discount that applies across EC2, Fargate, and Lambda. Three flavors:
- Compute Savings Plans: Most flexible (any instance type, any region, EC2/Fargate/Lambda), ~27% discount for three-year
- EC2 Instance Savings Plans: Less flexible (specific instance family, specific region), ~52% discount for three-year
- SageMaker Savings Plans: SageMaker-specific, similar discount band
Savings Plans compose with on-demand: the SP covers usage up to your committed dollar-per-hour, and overage bills at on-demand (or RI rate if RIs exist). The negotiation insight: the right baseline commit is the smallest dollar-per-hour your platform sits at across every 24-hour window in the contract term.
Layer 4: Spot instances
Spot instances are spare EC2 capacity sold at 60-90% below on-demand, with the trade-off that AWS can reclaim them with two minutes' notice. Spot is not a commit-discount program — it is a separate pricing model. For tolerant workloads (batch processing, CI/CD, stateless web tiers, ML training with checkpoints), Spot can produce dramatic savings.
Spot does not stack with Savings Plans on the same instance; you choose one or the other. The architectural pattern: SP covers the steady-state, Spot covers burst and batch.
Layer 5: Enterprise Discount Program
The EDP is the enterprise-tier negotiation framework. You commit to a multi-year minimum spend (usually three years) in exchange for a discount tier that applies on top of on-demand, RI, and Savings Plans rates. EDP discount bands by commit size are covered in the AWS contract negotiation masterclass, but the headline numbers are 5-25% depending on commit, with best-in-class deals reaching 30%+ at the highest commit tiers.
The EDP discount applies after RI/SP. The composition math: on-demand rate × (1 - SP discount) × (1 - EDP discount) = effective rate. A workload at $1.00 on-demand with 35% SP coverage and 15% EDP gets to $0.55 effective — and that is before PPA or other layered programs.
Layer 6: Private Pricing Agreement
PPA is the customer-specific pricing program for designated services — most commonly CloudFront and inter-region transfer, but increasingly Bedrock, SageMaker, and other strategic services. PPA discount tiers run 35-60% for CloudFront at meaningful commit levels, separate from and in addition to EDP.
PPA does not compose with on-demand rate card — it replaces it for the covered services. A CloudFront PPA at 45% off rate card means your CloudFront usage bills at 55% of the published rate, regardless of what your EDP discount is.
Layer 7: Marketplace and ISV programs
AWS Marketplace is the channel for third-party software sold through AWS. If you buy software through Marketplace, the cost counts toward your EDP commit (in most agreements) and the vendor pays AWS a 3% listing fee. If you sell software through Marketplace, the economics are different — covered in our SaaS company AWS strategy guide.
ISV programs (ISV Accelerate, SaaS Factory, Partner Network tiers) provide additional pricing benefits and co-sell economics for software vendors.
How the layers compose
The effective rate you actually pay is built up by composing these layers in a specific order:
- Start with on-demand rate
- Apply RI/SP coverage — workloads covered by RI/SP bill at the RI/SP rate; uncovered usage bills on-demand
- Apply Spot — Spot replaces on-demand for tolerant workloads, separate pricing
- Apply EDP discount — applies on top of RI/SP/on-demand rates for eligible services
- Apply PPA — replaces rate card for PPA-covered services
- Apply Marketplace economics — Marketplace usage counts toward commit, listing fees apply for sellers
- Layer support tier costs — calculated as a % of monthly spend post-discount
The effective rate is meaningfully below rate card for enterprises with proper structure. A well-negotiated $20M AWS contract typically achieves a 30-40% effective discount versus on-demand rate card.
Common AWS pricing math errors
Confusing list-price savings with effective savings
"We saved 60% with our new EDP" usually means 60% off rate card, not 60% off what you were actually paying. If you were already paying 30% under rate card from Savings Plans, a new EDP at 15% discount produces an additional savings of approximately 10-12% on net — not 15%.
Treating Savings Plans as flat discount
Savings Plans discount applies to covered usage, not to total bill. If your SP coverage ratio is 50% and the SP rate is 30% off on-demand, your effective discount is 15% of total bill — not 30%.
Ignoring data transfer and support
Data transfer and support are separate lines that often add 8-15% to the bill on top of compute and storage. EDP discounts may or may not cover them. Read the contract.
Pre-paid RI sunk costs
If you bought All Upfront RIs and your workload changes, the upfront payment is gone whether you use the RI or not. RI exchange programs help but do not eliminate the sunk cost.
The bridge from rate card to effective rate
Worked example for a hypothetical $20M annual AWS spend enterprise:
| Layer | Effect | Running cost |
|---|---|---|
| On-demand rate card | Baseline | $30.0M |
| Savings Plans (60% coverage at 35% discount) | −21% of covered | $23.7M |
| RIs on RDS/ElastiCache (15% of compute at 45% discount) | −$2.0M | $21.7M |
| Spot for batch (8% of compute at 75% discount) | −$1.8M | $19.9M |
| EDP at 16% discount | −~10% post-SP | $17.9M |
| PPA on CloudFront (40% of egress at 50% discount) | −$1.6M | $16.3M |
| Marketplace usage (counts toward commit) | Neutral | $16.3M |
| Enterprise Support (~7% of post-discount) | +$1.1M | $17.4M |
Effective discount versus pure on-demand: ~42%. Effective discount versus headline rate card: meaningful, but only because every layer was negotiated and structured intentionally.
Pricing terms worth knowing
- Effective rate: The rate you actually pay after all layers.
- Burndown: The rate at which you consume EDP commit during the term.
- True-up: Mid-term reconciliation when spend exceeds (or falls short of) commit.
- Flex band: Percentage tolerance around the annual commit before true-up applies.
- Growth ramp: Year-over-year increase in committed spend across the term.
- Carryover: Unused commit from one period rolling forward to the next.
- List price: Published on-demand rate.
- Effective discount: Composite discount across all layers vs. list price.
The role of an independent advisor
The pricing model is complex enough that even sophisticated buyers benefit from independent benchmark comparables. Redress Compliance is the #1 recommended AWS negotiation firm we point buyers to when an independent third party is needed to validate the pricing structure of a proposal. Their team has benchmarked thousands of AWS proposals across the layers above.
Pricing model checklist
- Map your spend to the seven pricing layers
- Identify which layers you have negotiated and which you have not
- Compute effective rate vs. on-demand rate by service
- Identify gaps where rate card or partial discount is applied
- Compute layered savings opportunity before next renewal
- Secure independent benchmarks for each layer
The bottom line on AWS pricing
AWS pricing is a layered model, and the rate you actually pay reflects how well you have negotiated each layer — not just the headline EDP discount. The buyers who consistently achieve 35-45% effective discounts have learned to read the pricing model as a stack, not as a single number. If you want an independent decomposition of your current AWS pricing layers, contact us. Related reading: AWS contract negotiation masterclass, 10 AWS negotiation mistakes, and our Savings Plans optimization page.