A real engineer should know better, but otherwise, it's people trusting what a major company claims.
If it was a fly by night organization I would totally agree with you, but Amazon is a major multinational. It seems to me as reasonable for an outsider to trust the claims they make as it is for me, a car industry outsider, to trust the claims that Chevrolet makes about my car.
Do you know how to properly quality evaluate everything in your life?
Hope you don't need a doctor, lawyer, or plumber soon.
However, for EBS volumes, Amazon is very clear about the expected data loss rate:
"The durability of your volume depends both on the size of your volume and the percentage of the data that has changed since your last snapshot. As an example, volumes that operate with 20 GB or less of modified data since their most recent Amazon EBS snapshot can expect an annual failure rate (AFR) of between 0.1% – 0.5%, where failure refers to a complete loss of the volume. This compares with commodity hard disks that will typically fail with an AFR of around 4%, making EBS volumes 10 times more reliable than typical commodity disk drives."
Thank you for the exceptionally clear counterpoint.
What it does say is this:
"As an example, volumes that operate with 20 GB or less of modified data since their most recent Amazon EBS snapshot can expect an annual failure rate (AFR) of between 0.1% – 0.5%, where failure refers to a complete loss of the volume.
Which to any engineer, "real" or otherwise, should be a pretty strong signal that something bad will happen.
The key to EBS is frequent S3 snapshots. The reliability issues of EBS only appears to the delta since your last S3 snapshot. Still... people use EBS w/o frequent S3 backups, amazingly.
Where do they do this? All the docs I've seen are pretty clear that EC2/EBS stuff could disappear and that you have to plan a fault-tolerant system.
EBS is fine as long as you're aware of the constraints and plan accordingly.
you have to assume any given drive image will disappear at any moment
Duh! You mean it behaves exactly as documented? That is outrageous.
They cluster their databases across multiple instances, availability zones and regions, and back them up constantly to S3. Their ultimate recovery plan is to restore from backup if necessary, which is pretty much the same as assuming EBS will corrupt your data.
While it's far from trivial to do it that way, they seem to be the most successful user of the AWS systems.
The only exception I've seen are people with very spiky traffic patterns, who can save a bit of money by only running instances when they need them - but even then I suspect that the money saved might be less than you'd think.
Amazon wins for APIs and convenience but not for price.
You can also raid EBS volumes together for realtime redundancy, but adds cost and complexity.
For people who don't want to spend the money on a hot standby, you can still produce the database log files from MySQL (or whatever you're using), and copy them off the machine onto S3 every few seconds, minutes, etc.
There's no end of solutions to the problem but, for whatever reason, a lot of people don't see EBS as a potential problem area.
At the same time, if you've not spotted by now that EBS (elastic block storage, which powers RDS) is not reliable and not to be trusted, then you have to look at yourself too.
EBS is by far the worst product AWS offer, you simply should not use it without a very good reason, and if you do need to use it, you have to assume any given drive image will disappear at any moment - as it did here.
Beyond that, any time you're running a database, no matter who the provider is, if you're not doing backups every day or hour, then you're not doing things right.