Subscribe free
Morning Merge · Sunday, November 1, 20264 min read

AWS's big capacity is largely booked through 2027

Plus Jepsen's 96 ParticleDB issues, a ChatGPT link exploit and one shared Codex allowance.

The main thing

An isometric cutaway of a warehouse packed wall to wall with plain freight crates, with a single orange loading bay kept clear beside the crowded storage floor.

If your capacity plan says "we'll grab more when we need it," give it a second look. The biggest blocks of AWS capacity are spoken for, and some teams say ordinary instances are getting harder to find too.

Amazon CEO Andy Jassy said on a podcast that AWS's large committed capacity is largely sold out through 2027, with a good chunk of 2028 gone too. Jassy also said AWS always leaves some room for on-demand, EC2 and Bedrock. So the restaurant is still open. The big tables are just booked for a while.

Cloud analyst David Linthicum argues the coverage overstated things, and suspects you can still allocate GPU capacity in the console today, just not a massive pre-reserved block.

The Reddit discussion was more worrying. The top comment describes trouble getting enough on-demand capacity for regular EC2 instances over the past month or so. It mostly hit CI, but production k8s clusters were "concerningly constrained" on a few days. Other commenters report similar trouble on Azure East US and across all three major providers. These are anecdotes, and AWS has published no data behind them here.

The natural reaction is to reserve everything just in case, which Ian Rae calls "an anti-cloud pattern."

What to do today: If a launch or large deployment is coming, confirm the capacity exists before you count on it. Check how CI behaves when an on-demand request fails. If you already hold reservations, EC2 Capacity Manager reports how much of them you actually use.

Quick bits

Also happening

Table for one in 2029, then?

← All issues

Get this in your inbox every morning.

Free. Five minutes. Unsubscribe in one click.

Subscribe free →