# Migrate\_to\_s3 task fails for placing too many requests

**URL:** <https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305>\
**Category:** Self-hosting\
**Tags:** s3\
**Created:** [11.Январь.2019 18:20:32 UTC](https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305 "2019-01-11T18:20:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [14.Январь.2019 10:32:15 UTC](https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305/3 "2019-01-14T10:32:15Z")

</div>

Weird I never hit that rate limit error… Do you have lots of small files?

Also, the `s3cmd sync` will “break” any attachments (they will lose their file name).

> [@marcozambi](#):
>
> Why are we depending on setting of environmental variables that can potentially brake the UI? Shouldn’t be the data we already put in the configuration via web UI enough for running the migrate\_to\_s3 task?

In theory, it should be. But it’s not convenient to set the arguments in one place (settings UI) and use them in another (rake task).

---

_[View the full topic](https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305)._