EC2 purchasing options: flexibility, commitment and interruption

Hi, I’m Bhavesh Atara from CloudFolks HUB. A lower advertised rate is only useful when the purchasing option fits your application. Let us compare flexibility and commitment with practical situations.

Understand normal usage

For a short lab or uncertain workload, flexibility matters. I would observe usage before considering a long-term commitment. A discount is useful only when it fits capacity or spending you will actually use over the commitment period.

Design for interruption

Spot capacity can suit work built to restart or resume. A batch job with checkpoints differs from a stateful server with no recovery plan. Decide how results are saved and retries happen before depending on interruptible capacity.

Keep capacity and discount separate

Savings Plans, Reserved Instances and Capacity Reservations address different requirements. Do not assume every discount reserves capacity. Review the current conditions for the chosen option and compare them with the Region, configuration and schedule of your workload.

Put the idea to work

Try it yourself

Compare a short lab, predictable service and restartable batch job. Explain the flexibility and interruption tolerance each needs.

A common question

Should I commit for my first lab?

Understand your usage first. A short experiment usually does not establish a reason for a long-term commitment.

References & video notes

Use the video to follow the topic with me. Console screens and older offers can change, so check the current AWS documentation before performing a lab.

Keep learning

All articles →