# Does using S3 for uploads mean redownloading all files when creating backups?

**URL:** <https://meta.discourse.org/t/does-using-s3-for-uploads-mean-redownloading-all-files-when-creating-backups/160273>\
**Category:** Product Support\
**Created:** [August 9, 2020, 4:56pm UTC](https://meta.discourse.org/t/does-using-s3-for-uploads-mean-redownloading-all-files-when-creating-backups/160273 "2020-08-09T16:56:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![lucasbasquerotto](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lucasbasquerotto/32/133376_2.png) [@lucasbasquerotto](https://meta.discourse.org/u/lucasbasquerotto)\
**Post date:** [August 14, 2020, 12:34pm UTC](https://meta.discourse.org/t/does-using-s3-for-uploads-mean-redownloading-all-files-when-creating-backups/160273/7 "2020-08-14T12:34:08Z")

</div>

In our case with a non-discourse site we use awscli to sync buckets (`aws s3 sync`) between **different regions** in **different accounts** , so even if an account was compromised and the bucket deleted, or if an asteroid falls and destroy an Amazon datacenter (hopefully not), we could recover from the other bucket. If you do a sync the costs should not be so high because only new/changed files will be synced.

Well, there is still the case of the 2 accounts being compromised in a short period of time and the buckets deleted or Amazon closing AWS, both **very very** unlikely. But if something like that occurs you can just play in the lottery, choosing the numbers you think are wrong 🙂

---

_[View the full topic](https://meta.discourse.org/t/does-using-s3-for-uploads-mean-redownloading-all-files-when-creating-backups/160273)._
