Never Put a Pet on an AWS Spot Instance
Post · https://dev.to/maame-codes/never-put-a-pet-on-an-aws-spot-instance-em3
I got a task at my internship that sounded simple. Move one of our servers to a new AWS region, keep...
First seen by Oriel on .
AI summary
This article explains why AWS Spot Instances suit replaceable servers but can endanger stateful servers whose data exists only on their attached disk.
- Spot Instances can be up to 90% cheaper, but AWS may reclaim them with two minutes’ warning.
- By default, interruption terminates the instance and may remove its attached disk, making recovery impossible for servers without separate storage.
- The article distinguishes replaceable “cattle” servers from stateful “pets,” recommending Spot for batch jobs, CI runners, test environments, and similar workloads.
- The team chose an on/off schedule with an on-demand instance, preserving its disk while avoiding compute charges when stopped.
- Spot may become viable after migrating the server’s data to safer external storage.
#aws spot instances #cloud cost optimization #devops #stateful servers
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Reactions
Total public reactions reported by the source; distinct from points and likes.
- DEV Community: 62, latest observation ; +9 over observed period since
Comments
Comment count reported by the source.
- DEV Community: 17, latest observation ; +15 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| DEV Community | 4924826 | https://dev.to/maame-codes/never-put-a-pet-on-an-aws-spot-instance-em3 Read discussion |