Skip to content

docs: explain private S3/RustFS bucket behavior #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Monibee-Fudgekins wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: explain private S3/RustFS bucket behavior #97

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ab982d9
docs: explain private S3/RustFS bucket behavior (closes #91)
Monibee-Fudgekins May 3, 2026
93d7207
Potential fix for pull request finding
Monibee-Fudgekins Jun 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/admin/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,22 @@ RUSTCHAT_REDIS_URL=redis://localhost:6379/
| `RUSTCHAT_S3_REGION` | No | `us-east-1` | S3 region |
| `RUSTCHAT_S3_PUBLIC_URL` | No | - | Public URL for file access |

> **Private bucket by design**
>
> RustChat stores uploaded files in a **private** S3/RustFS bucket by default. Uploaded objects are not
> accessible via unsigned direct object-store URLs — attempting to fetch them without a valid signature or
> presigned URL should return a `403 Forbidden` response. This is intentional: access to files is mediated
> by RustChat, either through authenticated RustChat endpoints or through time-limited presigned URLs that
> RustChat generates after authorising the requester. This design keeps files scoped to their workspace and
> prevents unauthorised access.
>
> **Do not change the bucket to public.** Making the bucket public removes this protection and exposes all
> uploaded files — including attachments in private channels — to anyone who knows or guesses an object URL.
>
> If you need to serve files via a CDN or reverse-proxy, configure it to work with authenticated RustChat
> endpoints or RustChat-generated presigned URLs rather than bypassing RustChat by pointing directly at the
> object store.

### CORS

| Variable | Required | Default | Description |
Expand Down