3 ms·
Interesting comment. So, what would you do if you were called by someone whose cloud account got hacked and wiped? Or whose cloud account got closed because of
by jacquesm 3y ago
Interesting comment. So, what would you do if you were called by someone whose cloud account got hacked and wiped? Or whose cloud account got closed because of 'unspecified suspicious activity on your account'? Of course that never happens, right?
- crazygringo 3y agoI feel like we haven't yet come up with the right models and vocabulary to express these kinds of risks, or maybe I just haven't heard it. Especially because your credentials to AWS are likely stored somewhere that would also store your credentials to your separate backup vendor -- so why would two cloud vendors provide any more protection than two products within one cloud vendor? It's clear to me how to model hardware failure, or accidental data loss. It's not clear how to model "hackers gain access to one set of credentials but not another" or "provider closes your account and won't give you your data".
- nielsole 3y agoYou can set up your S3 objects to have a mandatory retention period further reducing the risk of a wiped account. https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-ops-retention-date.html https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-... Also while I have heard many horror stories about suspicious account closures for many vendors, AWS at least currently seems to be on top of their game. I fully agree with your argument, just adding colour to it