Three travelers book the same hotel room for the same night, and they pay three completely different prices. One walks up to the desk and pays the full rate, no commitment, gone in the morning. One signs a year ahead and pays far less, whether or not they ever show. One takes the standby deal, cheapest of all, on the condition that they can be bumped the instant a full-price guest wants the room. None of them is wrong. Each price fits a different kind of certainty, and knowing which is which is most of cloud cost.

That is the middle of the cost movement on Learning Maps. The Ballroom opened it with the core flip, you rent capacity instead of owning it. These two rooms are the two levers you pull once you are renting: pay less for the load you can predict, and pay less for the data you have to keep. Same series, same rules: the story carries the lesson, the napkin map rewards watching, and every room splits the durable principle from the rented AWS label.

Episode 19. The Promise

Watch The Promise on YouTube (7:37).

Split your need by how sure you are of it. The steady baseline you run every hour of every day is the part worth a promise: commit to it for one year or three, and the discount is large, up to roughly seventy percent off with reserved instances or savings plans. The spiky, unpredictable part on top rides on on-demand, the walk-up rate, priciest per hour but owing nothing when idle. And the work that can be interrupted and simply retried, a batch job, a render farm, goes on spot, the standby deal, cheapest by far.

The one number people get wrong is the spot warning. When AWS wants the capacity back, spot gives you a two-minute notice, not five, so spot suits only work that can take an interruption and pick up again. And the terms are one year or three, not a sliding two, so the mental model is a step, not a dial. The shape to carry is a demand chart: a flat committed floor for the baseline, on-demand for the spikes above it, and spot for the interruptible work off to the side. Match each slice of the load to the pricing that fits how sure you are, and the bill falls without a single server changing.

Episode 20. The Shelf

Watch The Shelf on YouTube (9:09).

Two moves fix the storage bill, and one catch hides inside the second. The first move is right-sizing: measure the real load and match the machine to it, instead of paying for a ballroom to seat a book club of six. The second is tiering: hot data on fast, dear storage, cold data on cheap, slow storage, with lifecycle rules that migrate it down on their own as it ages. On AWS that ladder runs Standard, then Standard-IA, then the three Glacier tiers, priced by how long you will wait to get it back.

Here is the catch, and it is the thing the exam loves. The cheap shelf is not free, it is a bet: you are wagering you will rarely read this again. Win it and your per-gigabyte rate drops. Lose it and a retrieval fee claws the discount straight back. Worse, the cheap classes charge a minimum stay, thirty days for Standard-IA, ninety for Glacier, a hundred and eighty for Deep Archive, so a two-week file parked on a cheaper shelf still bills the full minimum and ends up costing more. Anything short-lived belongs on Standard, every time. And when you genuinely cannot predict the pattern, Intelligent-Tiering moves objects for you with no retrieval fees and no minimum, charging a small monitoring fee instead, the price of not having to guess. Tier down, but only what will truly stay down.

What the pair adds up to

The Promise is about what you run, the Shelf is about what you keep, and they rhyme. Both say the same thing: sort your load by how certain you are, then buy the cheapest option that certainty allows. The steady baseline earns a commitment; the truly cold file earns a cheap shelf; and the moment you are unsure, you pay a little more to stay flexible rather than betting wrong. Cost is not a discount you hunt for after the fact. It is a set of matches you make on purpose, up front.

One room remains, and it is the one that ties the whole series together: the Blueprint, where the biggest cost decisions turn out to live in the shape of the architecture itself. If you are just arriving, the map runs in order through the Data Wing, the coordination pair, the systems-talking wing ending at the Outpost, and the security wing closing at the Cipher. And if you want the frame the whole series sits on, there is AWS is math and Kubernetes is physics.