# Step-by-step for moving large site uploads to S3?

**URL:** <https://meta.discourse.org/t/step-by-step-for-moving-large-site-uploads-to-s3/94321>\
**Category:** Product Support\
**Created:** [August 9, 2018, 4:01pm 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:** 5

<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:** [August 9, 2018, 11:15pm UTC](https://meta.discourse.org/t/step-by-step-for-moving-large-site-uploads-to-s3/94321/5 "2018-08-09T23:15:27Z")

</div>

@Gunnar

Hmm, that’s odd. AFAIK the Uploads table should only reference the relative path, and not the full path to the image location. We had a couple of posts that ended up that way, but it was because the full path was referenced in the post, rather than using the image upload button or copy/pasting. Is this happening for _all_ posts, or perhaps a subset that use the full domain, rather than the relative path?

Either way, something like this _should_ work

```plaintext
remap https://forums.jag-lovers.com//jl-discourse-uploads.s3.amazonaws.com //jl-discourse-uploads.s3.amazonaws.com

```

You may need to tweak the input string, as I am not sure if you’ll need the `https://` or not, it’s best to take a look at either the Uploads table or the unbaked post to see what string your replacing.

---

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