

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
click for more info
Not enough gems
Cost: 6 gems
1: EC2 Instance Configuration: Keys
incomplete
2: EC2 Instances
incomplete
3: AMIs and Instance Types
incomplete
4: Public IPs
incomplete
5: Elastic IPs
incomplete
6: Security Groups
incomplete
7: SSH to Our Server
incomplete
8: Deploy the PatientPing Site
incomplete
9: Open Web Traffic
incomplete
10: Creating and Using Your Own AMI
incomplete
11: Reserved Instances and Savings Plans
incomplete
12: Auto Scaling Groups
incomplete
13: Launch Template
incomplete
14: Launch from Template
incomplete
15: Spot Instances
incomplete
16: Stateful and Stateless Applications
incomplete
17: Optional Cleanup
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Savings plans are great, but what if you want to save even more money? Allow me to introduce you to spot instances.
Imagine you're in AWS' shoes. You have to build out new racks of servers to keep up with demand, and you want to streamline things, so you install not just what you need today but what you think you'll need for the next few years.
This leads to a problem: what to do with all the new capacity that's not being used yet?
AWS lets you bid on this unused capacity with no long term commitment at a ~90% discount. With one small caveat.
Dear Zach,
I'll give you this massive discount, but be warned, at any time I may literally delete your server. Don't worry, I'll give you a 2-minute heads-up.
Love, Jeffy B
So, if you have a stateless application that only needs to do async or offline compute, spot instances might be the perfect choice. If a server dies, no worries, you can just start a new one and pick up where you left off.
But if you need to be always on, spot instances are not a good fit.