"S3 for backups is the single biggest ease-of-mind feature AWS provides, IMO. I do not want all my data sitting in a single colocation facility without backups.

"S3 for backups is the single biggest ease-of-mind feature AWS provides, IMO. I do not want all my data sitting in a single colocation facility without backups." I'm biased, but in my opinion if your infrastructure is on AWS and your backups are on AWS you're doing it wrong. Even accounting for zones and geo-disparity, etc. Luckily: ssh user@rsync.net rclone s3:/some/bucket /rsync.net/home ... which is made possible by rclone[1], which is excellent, and the fact that rsync.net has rclone built into the remote environment[2] such that you can execute it over SSH. [1] https://rclone.org/ https://rclone.org/ [2] https://www.rsync.net/products/rclone.html https://www.rsync.net/products/rclone.html