litvancom/ferrobucket repository overview

⁠ferrobucket

Lightweight, self-hosted, S3-compatible object storage with a built-in web UI — one static Rust binary.

ferrobucket is the S3 server (it stores objects on the local filesystem) — point your existing S3 tooling at it. It ships as a single static binary on a scratch image that idles around 2 MB of RAM.

🔗 Website: https://litvancom.github.io/ferrobucket/⁠ · Source: https://github.com/litvancom/ferrobucket⁠ · License: MIT

⁠Quick start

# anonymous (local/dev — skips SigV4)
docker run -p 9000:9000 -v ./data:/data \
  litvancom/ferrobucket --anonymous

# with a static credential
docker run -p 9000:9000 -v ./data:/data \
  -e FERROBUCKET_ACCESS_KEY=myaccesskey \
  -e FERROBUCKET_SECRET_KEY=mysecretkey \
  litvancom/ferrobucket

Then:

• S3 API + web UI: http://127.0.0.1:9000⁠ (UI at /ui)
• Point any S3 client at it (path-style): aws --endpoint-url http://127.0.0.1:9000 s3 ls

⁠Features

• S3-compatible API — bucket CRUD, get/put/head/delete, ListObjectsV2 (prefix + delimiter), DeleteObjects, multipart, presigned GET/PUT. Works with the aws CLI, boto3, rclone, s3fs and any SigV4 client.
• Built-in web UI — browse buckets/objects, drag-&-drop multipart uploads, image/text previews, presigned links, light & dark themes.
• Credentials stay server-side — SigV4 with a single static credential (or --anonymous). Keys never reach the browser.
• Tiny & self-contained — embedded assets, multi-arch scratch image, ~2 MB idle RAM. No database, no sidecars.

⁠Configuration

• Volume: mount a host directory at /data for persistence.
• Port: 9000 (S3 API + web UI on the same port).

⁠Supported tags

• latest, 0.1.0 — linux/amd64, linux/arm64

⁠Status

Pre-1.0. Targets local development and homelab use — not production/distributed storage. See the README⁠ for AWS-S3 behaviour deviations.