No matter how good you think a given "cloud" solution is, no matter how much too big to fail you thing the company responsible is, you should make use of the redundancy options they provide and make sure you have reasonable backups elsewhere too (local to you or on another completely separate remote service).
This is what made me dismiss Google's App Engine when it first turned up (I've not looked for some time, they may have addressed this concern long ago): there was no easy way to backup all your data to another location/service and the not-so-easy ways would probably all end up costing a fair bit in bandwidth charges.
I meant cloud solution should not have storage failures which causes data loss.
Would you have preferred they only offered Multi-AZ databases? (and in the process doubled your development, staging and QA environment costs..)
Would you mind defending your expectation that other people and companies will give you extra services for free?
Amazon has been very clear on the expected failure rate of ebs volumes and the attendant rds failures. If you want data safety, multi-az deployment offers it.
You mean you think all cloud db solutions should implement replication for you? There aren't very many backup solutions that never lose any data.