The monster under the bed was always in the contract

A remarkable number of cloud strategies are built on assumptions that never made it into a contract.

For years, many cloud teams repeated the same lines to management with confidence: AWS never raises prices. AWS does not shut services down. Things only ever get better with time. These beliefs were rarely challenged, largely because history seemed to support them.

Crucially, they were not contractual guarantees.

They were habits of thought, reinforced by past behaviour and repeated long enough to feel solid. They shaped financial models, commitment strategies, and executive reporting. Risk registers stayed quiet.

That is why the recent changes matter. They are not dramatic. They are clarifying.

If something sits in your assumptions but not in your contract, it is not protection. It is risk. And risk belongs explicitly in your systems, not implicitly in your plans.

When prices fall, AWS makes noise

In June 2025, Amazon Web Services announced GPU price reductions of up to 45 per cent. The message was everywhere: blog posts, press releases, headlines. AWS was once again ‘passing scale on to customers’.

This was intentional. Falling prices were part of the AWS story.

When prices rise, AWS stays silent

In January 2026, AWS raised GPU prices by roughly 15 per cent. There was no announcement.

On Saturday 4 January, the p5e.48xlarge instance–eight NVIDIA H200 GPUs – increased from $34.61 to $39.80 per hour. For teams running continuous workloads, that is around $3,700 more per month per instance. The change was discovered by journalists, not customers. No email. No blog post. No explanation.

The asymmetry matters.

AWS wanted credit for the reduction. It did not want attention for the increase. Both applied to the same instance families. Only one was treated as news.

This is not about intent. It is about structure.

The end of a convenient belief

For a long time, AWS benefited from a widely shared assumption: prices do not go up.

That assumption was never guaranteed. Prices did rise indirectly through generational changes and rebalanced offerings. But the overall direction was stable enough that many organisations treated it as safe.

This time, there was no generational shift to hide behind. Prices went up because AWS could raise them.

The assumption broke because it was no longer useful to maintain it.

Price reductions used to be the point

The shock is sharper because early AWS behaved very differently.

In its first decade, AWS cut prices regularly, visibly, and proudly. Falling prices were a feature, not a side effect. Amazon S3 is a good illustration, with repeated reductions as infrastructure matured and scale increased.

AWS even formalised the habit. Price reductions had their own RSS feed and a dedicated category on the AWS News blog. It was deliberately noisy.

That rhythm slowed around 2016 and never returned.

The feed still exists, but the pattern tells its own story. In 2020, AWS announced five price reductions. In 2021, six. In 2022 and 2023, one each. In 2024, five. In 2025, three. In 2026, so far, none. The last update dates from August 2025.

This is not random. It is structural.

What the contract actually guarantees

The gap between assumptions and reality appears clearly in AWS contracts.

AWS publishes a comprehensive set of service-level agreements. Almost without exception, they cover uptime. Not performance. Not throughput. Not latency. Availability.

Take Kinesis. Its sole purpose is to move data. Yet its SLA says nothing about how fast data moves, how delayed it may become, or what happens when pipelines back up. If the service is technically ‘up’, the SLA is met.

This is the rule, not the exception.

AWS contracts protect against outages, not degradation. You can receive a clean uptime report while systems slow down, queues build up, and costs rise elsewhere to compensate. Contractually, nothing has gone wrong.

Once again, the assumption lives outside the agreement.

Reserved Instances, Savings Plans, and the price-rise question

This is where things become concrete.

When prices move, the first question executives should ask is simple: what did we actually lock in?

Reserved Instances do lock in a specific price for a specific configuration, for the duration of the term. If you bought a three-year all-upfront Reserved Instance before the GPU price increase, that price does not change. In that narrow sense, you are protected. In fact, you may now be saving more than you expected, because the on-demand reference price has risen around it.

Savings Plans are different.

Savings Plans do not lock a price. They lock a discount relative to on-demand pricing. When the underlying price rises, the absolute cost you pay rises with it, albeit at a discounted rate. Your commitment remains, but the value you thought you were getting may shift.

This distinction matters, and it is often misunderstood.

A price increase can make existing Reserved Instances look unusually valuable, while simultaneously making Savings Plans more expensive in absolute terms. The same event can improve one position and weaken another.

That is not a bug. It is how the contracts are written.

The uncomfortable part is that many technical and financial teams implicitly assumed price rises were ‘not possible’, and therefore never modelled these scenarios. That assumption is now demonstrably false.

AWS is behaving like a normal business

None of this makes AWS unusual.

Supply is constrained. Input costs are rising. Alternatives face similar limits. Pricing power exists, and AWS is using it. Commitments are being reshaped. Lock-in is being reinforced. Revenue is being made more predictable.

From an investor’s perspective, this is rational behaviour. AWS becomes easier to model, easier to value, easier to defend as a business within Amazon.

Whether this ever leads to formal separation or an IPO is secondary. The operating logic is already visible.

A practical recommendation for executives

The right response is not panic. It is review.

Executives should ask their legal teams to examine their AWS contracts and identify precisely where benefits come from. In most cases, those benefits exist because some risk has been accepted in return. That is fair. Risk and reward always travel together.

What matters is whether those risks are visible, owned, and proportionate.

Pricing volatility. Performance degradation without breach. Silent changes to commercial conditions. Commitment value shifting as prices move. These are not failures of AWS. They are features of the agreement.

Reseller and large enterprise customers should be particularly careful. Their contracts are often customised, layered, and amended over time. What feels like ‘standard AWS behaviour’ may in fact be a specific trade-off negotiated years ago and never revisited.

Contracts age. Assumptions harden. Risks go stale.

Top-down FinOps starts by moving assumptions out of folklore and into the risk register. If a risk is acceptable, write it down. If it is material, model it. If it is unbounded, renegotiate it or plan around it.

AWS is very clear about what it guarantees.
The danger begins when customers are not.