# Schritt-für-Schritt-Anleitung zum Verschieben großer Site-Uploads nach S3?

**URL:** <https://meta.discourse.org/t/step-by-step-for-moving-large-site-uploads-to-s3/94321>\
**Category:** Product Support\
**Created:** [9. August 2018 um 16:01 UTC](https://meta.discourse.org/t/step-by-step-for-moving-large-site-uploads-to-s3/94321 "2018-08-09T16:01:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mmayo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mmayo/32/119577_2.png) [@mmayo](https://meta.discourse.org/u/mmayo)\
**Post date:** [9. August 2018 um 20:06 UTC](https://meta.discourse.org/t/step-by-step-for-moving-large-site-uploads-to-s3/94321/2 "2018-08-09T20:06:17Z")

</div>

We recently went through this process, and there are a couple of ways to do it, the safe and slow way, using the `migrate_to_s3` rake task:

> <https://github.com/discourse/discourse/blob/0879610ffd9ef9f9b29a0ebaa4cb9535434dd61b/lib/tasks/uploads.rake#L111>

I think you could go ahead and turn on s3 uploads (there are a number of guides), and possible ssh into your container and run this task, and you wouldn’t experience downtime.

We didn’t go this route because it takes ~15 seconds per upload, and this was going to take days. We were doing this as part of a host migration, and couldn’t have a downtime of that long.

The quick and dirty route is as follows:

1. Enable S3 Uploads on your site
2. Back up your site with images, and download the archive.
3. Unzip the the archive, and navigate to `uploads` sub-folder, and upload the images to s3, using the aws-cli:

```plaintext
uploads aws s3 cp . s3://<your-s3-bucket> --recursive --acl public-read

```

4. We then need to [remap](https://github.com/discourse/discourse/blob/master/script/discourse#L5) all of the references to the public uploads folder to the new location in s3. At the console in your docker container:  
` root@dc53d70f611c:/var/www/discourse# discourse remap /uploads/default/ //<your-s3-bucket>.s3.amazonaws.com/ Rewriting all occurences of /uploads/default/ to //<your-s3-bucket>.s3.amazonaws.com/ THIS TASK WILL REWRITE DATA, ARE YOU SURE (type YES) YES Remapping ar_internal_metadata key 0 rows affected! Remapping ar_internal_metadata value ... many more rows `

We did the above during a scheduled maintenance window, and the site was in read only mode with a fresh backup on hand, so it was pretty low risk. I’m not sure I’d be comfortable doing it any other way, but it took less than an hour.

---

_[View the full topic](https://meta.discourse.org/t/step-by-step-for-moving-large-site-uploads-to-s3/94321)._