# How does one configure an S3 bucket and restore backups from it?

**URL:** https://meta.discourse.org/t/how-does-one-configure-an-s3-bucket-and-restore-backups-from-it/356233
**Category:** Support
**Tags:** install
**Created:** [March 7, 2025, 11:18am UTC](https://meta.discourse.org/t/how-does-one-configure-an-s3-bucket-and-restore-backups-from-it/356233 "2025-03-07T11:18:00Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![qingfeng1024](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/qingfeng1024/32/495412_2.png) [@qingfeng1024](https://meta.discourse.org/u/qingfeng1024)
#### Post date: [March 7, 2025, 11:18am UTC](https://meta.discourse.org/t/how-does-one-configure-an-s3-bucket-and-restore-backups-from-it/356233/1 "2025-03-07T11:18:00Z")

</div>

How does one configure an S3 bucket and restore backups from it?

When utilizing an S3 bucket, is it necessary to input the following variables beneath the env variables in the app.yml file, or is it sufficient to configure them solely within the admin settings?

```plaintext
  DISCOURSE_USE_S3: true
  DISCOURSE_S3_REGION: us-west-1
  DISCOURSE_S3_ACCESS_KEY_ID: myaccesskey
  DISCOURSE_S3_SECRET_ACCESS_KEY: mysecretkey
  DISCOURSE_S3_CDN_URL: https://falcoland-files-cdn.falco.dev
  DISCOURSE_S3_BUCKET: falcoland-files
  DISCOURSE_S3_BACKUP_BUCKET: falcoland-files/backups
  DISCOURSE_BACKUP_LOCATION: s

```

When I enabled only the S3 bucket in the admin settings, I downloaded the backup files from S3 to migrate to a new server and restore the backup. Everything was done according to the forum’s tutorial, yet the restoration of the backup failed, much like the situation described in this post.

> [@Restore from backup fails due to S3 migration](https://meta.discourse.org/t/restore-from-backup-fails-due-to-s3-migration/127409/8):
>
> I solved; I open dump.sql with EmEditor program and search enable\_s3\_uploads, S3 and all “t” to “f” all “true” to “false”. Restore successful slight_smile

The ultimate solution steps are as follows:

> That’s a known problem. As a workaround, you could temporarily disable the enable\_s3\_uploads site setting before creating the backup. You can re-enable on the new server after the restore.

How might one properly utilize the restoration of backups from an S3 bucket in the event that my server becomes inoperable due to a crash, virus infection, or severe attack, necessitating the download of backup files from the S3 bucket and the subsequent restoration of these backups on a new server?

Thank you for any advice offered by anyone!

---

<div class="post-metadata">

### Author: ![copymonopoly](https://avatars.discourse-cdn.com/v4/letter/c/4491bb/32.png) [@copymonopoly](https://meta.discourse.org/u/copymonopoly)
#### Post date: [March 12, 2025, 12:53am UTC](https://meta.discourse.org/t/how-does-one-configure-an-s3-bucket-and-restore-backups-from-it/356233/3 "2025-03-12T00:53:41Z")

</div>

This is a very serious issue. Does this mean that the backups in S3 are meaningless?

---

<div class="post-metadata">

### Author: ![qingfeng1024](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/qingfeng1024/32/495412_2.png) [@qingfeng1024](https://meta.discourse.org/u/qingfeng1024)
#### Post date: [March 12, 2025, 12:58am UTC](https://meta.discourse.org/t/how-does-one-configure-an-s3-bucket-and-restore-backups-from-it/356233/4 "2025-03-12T00:58:16Z")

</div>

After numerous attempts, I have found that backups in S3 cannot be restored at will. I have consulted many posts, all of which report that restoring backups from S3 has failed.

I sincerely hope someone can summarize how to configure S3 backups and how to restore them from S3.

---

<div class="post-metadata">

### Author: ![copymonopoly](https://avatars.discourse-cdn.com/v4/letter/c/4491bb/32.png) [@copymonopoly](https://meta.discourse.org/u/copymonopoly)
#### Post date: [May 15, 2025, 8:05pm UTC](https://meta.discourse.org/t/how-does-one-configure-an-s3-bucket-and-restore-backups-from-it/356233/5 "2025-05-15T20:05:43Z")

</div>

Hello, I’m quite concerned about whether this issue has been resolved. I would kindly suggest moving the topic to the **bug** category so that it can receive more appropriate attention.
