EC2 instances don't come with vmotion. It's up to the customer to detect a failed/retired node and restart on another EC2 instance.
The first thing you discover when reading through the various options is that you need to treat ALL local storage like /tmp, subject to deletion at will. Keep your persistent storage on EBS/S3.
And even if you do keep your important stuff on EBS, make sure you take snapshots on a frequent basis. We have received this email a couple of times:
Your volume experienced a failure due to multiple failures of the
underlying hardware components and we were unable to recover it.
Although EBS volumes are designed for reliability, backed by multiple
physical drives, we are still exposed to durability risks caused by
concurrent hardware failures of multiple components, before our systems
are able to restore the redundancy. We publish our durability expectations
on the EBS detail page here (http://aws.amazon.com/ebs).
Sincerely,
EBS Support
Fortunately, we had recent snapshots and it was a matter of (manually) spinning up a new instance from those.
Comments
EC2 instances don't come with vmotion. It's up to the customer to detect a failed/retired node and restart on another EC2 instance.
The first thing you discover when reading through the various options is that you need to treat ALL local storage like /tmp, subject to deletion at will. Keep your persistent storage on EBS/S3.
And even if you do keep your important stuff on EBS, make sure you take snapshots on a frequent basis. We have received this email a couple of times:
Fortunately, we had recent snapshots and it was a matter of (manually) spinning up a new instance from those.Edit: proper quotation