* Rich Freeman <ri...@gentoo.org> [150509 09:00]: [..SNIP..] > One thing you can't cheaply do with Amazon is verify your backups. > Duplicity will happily check the data files against the manifest > hashes with a simple command, but it will cost you 10c/GB for whatever > you verify, since it will need to be transferred out. I guess another > option is to launch an EC2 instance with duplicity on it and have it > do the verify. That would be an internal Amazon transfer which is > both free and much faster, but it will cost you a few cents per hour > for the CPU time. I also don't know if duplicity can verify a backup > without the encryption keys - if it can't then you'll have to upload > your keys to EC2 which means Amazon could read your backups if they > wanted to. Otherwise duplicity is encrypting locally and all Amazon > does is store a bunch of encrypted data and regurgitate it on demand. > > -- > Rich
Thanks for the great post Rich. As for keys, you could use Amazon's AWS Key Management Service. Of course they could be sitting there gathering keys, but at some point you either have to trust they'll do what they say or simply decide not to use them at all (IMNHO.) You could also use AWS Key Management for backup data you want "reasonably" secured and then your own keys for data you want more highly secured (hopefully much smaller so the verify costs are more reasonable.) Todd
