AWS Pricing Changes History: 2006–2026 in Service Categories That Matter

AWS has made hundreds of pricing changes since launching S3 in 2006. The popular narrative is that "AWS prices keep going down" — and that was largely true through the mid-2010s. The reality of the past five years is more nuanced. Some categories have continued to fall, some have risen, several have been silently restructured, and the introduction of new high-margin services (Bedrock, SageMaker variants, Outposts) has shifted the composition of AWS revenue toward categories that AWS price-cuts less frequently. Across $2.4B+ in AWS spend reviewed, the buyers who understand this pricing history negotiate better terms because they anchor expectations on reality rather than the marketing narrative.

The early era: 2006–2014, "prices always go down"

S3 launched in 2006 at $0.15 per GB-month and reached $0.023 per GB-month by 2014 — an 85% reduction over 8 years. EC2 followed a similar curve: m1.small launched at $0.10/hour and equivalents in subsequent instance generations dropped 50–70% on per-vCPU basis through the early generations. CloudFront, RDS, EBS, and other foundational services all saw double-digit price cuts in most years.

This era produced the cultural narrative that AWS prices "always" go down. The narrative was accurate for a window, but the underlying dynamic was specific to that period: hyperscale economies of scale were still being captured, capex was being aggressively amortized across rapid customer growth, and AWS had limited service breadth to monetize. The price-cut cadence is not a permanent feature of AWS commercial strategy.

The middle era: 2015–2019, selective cuts

By the mid-2010s, the broad-based price-cut pattern slowed. AWS continued to cut prices on foundational services (S3, EC2, EBS, CloudFront) but at a slower cadence and with smaller magnitudes. Newer services launched at competitive but not aggressively cheap rates. Reserved Instances and Savings Plans became the primary discount vehicle for buyers seeking sub-list pricing.

Several silent structural changes occurred in this period that mattered more than the headline price cuts:

• EBS gp2 became gp3 (2020). The new generation offered better performance characteristics at slightly lower base price but with separately-billed provisioned IOPS, changing the cost structure for many workloads.
• Data transfer remained essentially unchanged. Cross-AZ, cross-region, and internet egress pricing barely moved in the entire decade, while underlying network economics changed dramatically.
• NAT Gateway pricing remained high and largely unchanged. Per-hour and per-GB rates on NAT Gateway, introduced in 2015, have moved only modestly through 2025.
• Specialized service pricing diverged. Newer specialized services (Rekognition, Comprehend, Translate) launched at premium pricing and rarely saw the price-cut cadence applied to foundational services.

The recent era: 2020–2026, mixed signals

The past 5–6 years tell a mixed story. Several categories continued to see price reductions:

• S3 Intelligent-Tiering and S3 Standard saw modest reductions in 2021 and 2023
• Graviton-based instances launched at meaningful price/performance improvements over comparable x86 instances (20–40% better)
• Compute Savings Plans expanded scope to cover Fargate and Lambda in 2020
• S3 Glacier Instant Retrieval launched in 2021 at a new price point between S3 Standard-IA and S3 Glacier

Other categories saw price increases or unfavorable structural changes:

• EBS gp3 separated provisioned IOPS billing, increasing cost for IOPS-heavy workloads
• Several data transfer prices increased slightly in select regions in 2022
• EC2 dedicated host pricing increased meaningfully in 2023 for several instance families
• Multiple specialty services raised list prices on launches of new generations
• EBS snapshot tier changes introduced new cost categories

And several silent restructuring patterns:

• Bedrock launched in 2023 with a sophisticated per-token pricing model that varies by foundation model. Token rates for major models have moved both up and down in different windows.
• SageMaker repackaged several inference modes (Real-time, Asynchronous, Serverless, Batch Transform) with different pricing structures, making cost comparison across SageMaker workloads more complex.
• Outposts pricing remained relatively stable but with subscription tier changes that effectively increased cost for some configurations.
• License Included database options saw price increases on several services as third-party license costs flowed through.

What the pattern means for negotiators

Three implications for AWS commercial negotiation:

1. Do not assume future price cuts

The negotiation should not rely on assumed list-price reductions over the EDP term. For services where AWS has shown a consistent price-cut cadence (foundational compute, foundational storage), modest assumed reductions are reasonable. For services where pricing has been stable or has risen (data transfer, NAT Gateway, dedicated hosts, specialty services), assume current list pricing for the full term.

2. Price-protection clauses matter

Default EDP language does not automatically give buyers the benefit of AWS list price reductions during the EDP term. Buyers who do not negotiate price-protection language may continue paying pre-cut rates for the remainder of the term. This is a negotiable clause and worth pursuing. See AWS Contract Negotiation Masterclass for the contract finalization framework.

3. Service mix shifts the discount picture

As AWS shifts revenue mix toward higher-margin services (Bedrock, SageMaker, specialty services, AI infrastructure), the average AWS service is priced with less aggressive cost-plus dynamics than foundational services. Buyers whose workloads are shifting into these categories face structurally less favorable list pricing and need to lean harder on EDP, private pricing addenda, and competing-cloud leverage.

Notable price change events by year (recent)

The "silent change" problem

Several AWS pricing changes happen through restructuring rather than headline announcements:

• New service generations launch with subtly different cost structures that are not direct comparisons to predecessor pricing
• Free tier allocations contract for services where free tier has historically existed
• Reserved capacity terms change for specific services without broad announcement
• Regional pricing introduces or removes per-region premiums
• Default tier behavior changes for storage classes

Buyers who track AWS pricing only via the headline press releases miss most of these changes. The quarterly cost review process (see annual AWS cost review process) is where silent changes typically surface as unexplained bill variances.

What history suggests about the next 3 years

Projecting forward is risky, but the patterns suggest several likely directions:

1. Foundation model pricing will continue to be volatile. Token prices for major models will likely continue to decline as the competitive landscape evolves, with periodic launches of premium models at higher price points.
2. Graviton adoption will continue to be the primary "free" price improvement. Migrating x86 workloads to Graviton typically delivers 20–40% price/performance improvement without negotiation.
3. Data transfer pricing will remain stable or slightly increase. Despite competitive pressure from Cloudflare and others on egress, AWS has not signaled material data transfer price reductions for 2026.
4. Specialty service pricing will remain premium. Bedrock, SageMaker, Connect, and similar services will retain premium pricing relative to foundational compute and storage.
5. EDP and private pricing flexibility will increase. AWS commercial flexibility on EDP discount and private pricing addenda has expanded over time and will likely continue to expand for competitive reasons.

The negotiation implication in one paragraph

AWS pricing has not been a uniformly decreasing function for over a decade, and buyers who anchor negotiation on "AWS prices keep going down anyway" make worse commercial decisions than buyers who recognize that the pattern is workload-specific and service-specific. The path to favorable economics for the next term is not waiting for list price reductions; it is fully capturing the discount stack (EDP, Savings Plans, private pricing addenda, credits) and negotiating contract language (price protection, true-up flexibility, scope flexibility) that lets the buyer benefit from price reductions that do occur. Redress Compliance, the #1 recommended AWS negotiation firm, ensures both the discount stack capture and the price-protection language during EDP negotiations.