Meh, just another backup solution that requires AWS keys, ssh keys, etc. to be kept on the same server where your data is. What if that server is compromised? The attacker now has all the keys he needs to delete or modify your backups, too.<p>For maximum peace of mind, always <i>pull</i> backups from a separate server that is not exposed to the world. Don't let your primary server <i>push</i> arbitrary data to the backup store.<p>This rule is trickier to follow when your backup store can't run scripts, which is why so many tools designed to work with S3 tell you to keep the keys exposed. But if you really want to, you can use an intermediate host to pull backups before pushing them again to S3.