Overview

S3 Storage provisions a SeaweedFS S3 gateway as Docker container foster_s3engine on foster_network. The panel shows status, endpoint, credentials, buckets, objects, and access keys.

External clients must use path-style S3 addressing and region us-east-1 against the endpoint shown in the panel.

Install

One-click install generates a random host port (typically 45001–50000), admin keys, and opens the firewall for that port.
Setup progress streams in the UI while the image pulls and the container starts.
Uninstall can optionally remove the data volume — destructive and may require step-up confirmation.

Buckets & objects

Create, list, and delete buckets (delete empties objects first).
Browse folder-style listings; object lists are capped (on the order of ~200 keys per page).
Preview/download chunks are size-limited; panel uploads are intentionally small-cap for safety.

Access keys

Create extra access keys — the secret is shown once.
Assign permission presets (admin, read/write, read-only, bucket-scoped, or none).
IAM changes apply live without restarting the container.
The primary foster_admin key cannot be deleted or have its policy changed from the panel.

Notes

Exposing the S3 port publicly means anyone with valid keys can reach your storage. Treat credentials carefully; prefer network restrictions and least-privilege keys.