Skip to content
BENIBIX Learn

Reserved and Spot Instances

Level 4 · Running and paying

Four ways to pay less for the same cloud server: rightsizing, reserved instances, savings plans and spot. What each one asks of you in return.

Course contentsLesson 11 of 11

After this lesson you can

  • Rightsize a server that is too big
  • Compare reserved instances, savings plans and spot
  • Pick the right price for a job

12 mincovers 4 glossary entries

Worth reading first: FinOps and Cloud Bills

Four ways to pay less for the same server

There are four main ways to cut a cloud bill. Rightsizing shrinks servers that are too big. A reserved instance or a savings plan trades a one or three year promise for a lower price, up to 72% off. A spot instance rents spare capacity for up to 90% off, but can be taken back.

Each one trades something for the discount. Rightsizing costs some care. A reservation costs a promise. Spot costs the right to keep your server.

Rightsizing comes first, because it is free. Many cloud servers use a small share of what they pay for. A server with 16 vCPUs that never uses more than 2 can drop to a 4 vCPU type and cost about a quarter as much.

A reserved instance is a promise to use one server type, in one region, for one or three years. A savings plan is a promise to spend a set amount each hour instead, on any type you like. Both suit servers that run all day, every day.

A spot instance is a spare server the cloud sells cheap. When the cloud needs it back, it gives a warning, often just two minutes, then takes it. That suits work that can stop and start, like batch jobs or test runs.

The full price, with no promise, is called on-demand. It is the right price for new work you cannot predict yet, and for short tests. Most teams mix all four: a reserved base, on-demand for growth and spot for batch work.

The mistake is to reserve before rightsizing. A three year promise on a server twice the size you need locks in the waste for three years. Shrink first, then reserve what is left.

The ways to pay for one server

PriceDiscountYou promiseThe catch
On-demandNoneNothingThe top price
Savings planUp to 72%An amount each hour, 1 or 3 yearsYou pay even if you use less
Reserved instanceUp to 72%One server type, 1 or 3 yearsStuck with that type
Spot instanceUp to 90%NothingCan be taken back at short notice

Which one to pick

  1. 1

    Rightsize

    Always, first. Shrink any server that never uses most of what it has.

  2. 2

    Reserve or plan

    For servers that run all day, every day, and will for a year or more.

  3. 3

    Spot

    For work that can stop and start again, like batch jobs and test runs.

  4. 4

    On-demand

    For new or short work you cannot predict yet.

The bigger the promise, or the more you let the cloud take back, the lower the price.

Worked example

A data team cuts its bill in half

A data team spends 20,000 euros a month on cloud servers, all on-demand. Their main servers average 15% busy.

They rightsize first, then reserve the steady base for one year and move nightly reports to spot. The bill falls to about 9,000 euros a month.

The words for this lesson4

Check yourself

Which job suits a spot instance best?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.