# 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:** 3
**Page:** 1
### Author:  [@Eviepayne](https://meta.discourse.org/u/Eviepayne)
#### Post date: [April 21, 2026, 7:33pm UTC](https://meta.discourse.org/t/discourse-logs-sent-to-wrong-s3/401176/1 "2026-04-21T19:33:59Z")
I was recently doing some cleanup of old files and infrastructure that I no longer needed after running this forum for a while.
I went through a migration of S3 a couple times and I just recently discovered my upload and email logs are still being uploaded to the first S3 ever configured.
I cannot find in the database where this is declared. My app.yml doesn’t point to aws (the first S3) at all.
Where can I find this in the database?
---
### Author:  [@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")
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.
---
### Author:  [@Eviepayne](https://meta.discourse.org/u/Eviepayne)
#### Post date: [April 26, 2026, 3:11pm UTC](https://meta.discourse.org/t/discourse-logs-sent-to-wrong-s3/401176/3 "2026-04-26T15:11:20Z")
This is unlikely.
The old S3 was a few migrations ago.