# Discourse logs sent to wrong S3

**URL:** https://meta.discourse.org/t/discourse-logs-sent-to-wrong-s3/401176
**Category:** Support
**Created:** [April 21, 2026, 7:33pm UTC](https://meta.discourse.org/t/discourse-logs-sent-to-wrong-s3/401176 "2026-04-21T19:33:59Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [April 25, 2026, 8:15pm UTC](https://meta.discourse.org/t/discourse-logs-sent-to-wrong-s3/401176/2 "2026-04-25T20:15:59Z")

</div>

Could it be outside Discourse itself?

For example, perhaps `app.yml` as a bind mount to a host directory, or there is an implicit bind mount from the container to the host, and that host directory is still being synced/backed up to the old S3 bucket by something like `aws s3 sync`, `rclone`, a cron job, or a backup script.

If `app.yml` no longer references the old AWS/S3 settings, I’d probably check the host for scheduled jobs or sync scripts next.

---

_[View the full topic](https://meta.discourse.org/t/discourse-logs-sent-to-wrong-s3/401176)._