2 ms·
This is definitely doable, but it's harder than the naive solution so often it's not done. Same as log storage for example, or any other incremental data. Rela
by viraptor 6y ago
This is definitely doable, but it's harder than the naive solution so often it's not done. Same as log storage for example, or any other incremental data.
Related - see how many examples of S3 policies split access into read and write rather than read, append, write. It doesn't even matter where the logic lives - only whether the storage service allows you to delete anything.
- user5994461 6y agoS3 is easy to handle but not intuitive. S3 always get write access from production systems because gotta be able to send the backup (anything strategy that aims to prevent writing to S3 is doomed). The trick is to get another S3 account (or any large storage really), to download everything from that bucket periodically. The "replication" needs read-only access to the first bucket. The second account doesn't need to be accessed by anything or anybody so it is relatively safe.
- viraptor 6y agoVersioned buckets and denying delete gives you an equivalent of an append-only backup. (As long as your backup tool supports that)
- user5994461 6y agoUntil the next developer/sysadmin comes along and update the bucket permissions to be able to send backups from yet another production system. :D