Deploy RustFS
S3-compatible object storage with persistent data, generated credentials, and a web console.
RustFS
Just deployed
/data
Deploy RustFS on Railway
S3-compatible object storage with a separate administration console. This template runs the official rustfs/rustfs:1.0.6 image, the latest stable release verified on November 17, 2026.
Included configuration
- Persistent
/datavolume and explicitRUSTFS_VOLUMES=/data. - S3 API on port 9000 and web console on port 9001, with a Railway HTTPS domain for each listener.
- Independently generated root access and secret keys; no shared default password.
- Railway startup readiness check at
/health/readyon port 9000, with a 300-second timeout and bounded restart retries. - The official image entrypoint is retained. No startup package downloads or custom shell wrapper.
First deployment
- Open Settings > Networking and identify the domain targeting port 9001. Open that domain to access the console.
- Retrieve
RUSTFS_ACCESS_KEYandRUSTFS_SECRET_KEYfrom the service Variables tab and sign in. Keep these credentials private. - Create a bucket and least-privilege application credentials. Do not embed root credentials in a browser or mobile application.
- Configure your S3 SDK with the HTTPS domain targeting port 9000, the generated application credentials, and path-style addressing unless you have explicitly configured virtual-hosted buckets. Do not use the console domain as the S3 endpoint.
The two public domains are distinct. Check their target ports rather than assuming RAILWAY_PUBLIC_DOMAIN identifies the console.
Production considerations
This is a single-node installation on one Railway volume, not a replicated cluster or a substitute for backups. Keep one replica. Choose a volume size for the stored objects and configure scheduled backups plus an off-platform recovery plan appropriate to your data.
Railway volumes are root-owned; RAILWAY_RUN_UID=0 makes the mount writable by this official non-root image. Do not remove that override unless you provision the volume ownership for the image user. A hardened custom image can initialize ownership and drop privileges, but this template does not silently replace the upstream entrypoint or use world-writable permissions.
Use HTTPS, rotate root credentials, configure CORS to the actual application origins, and restrict administration access where possible. Large uploads, streaming, and S3 client timeouts must also fit Railway's current HTTP proxy limits. Logs are available through Railway; object durability depends on the persistent volume, not the container filesystem.
Version upgrades are explicit: back up the volume, review release notes, then update the image tag. Updating this marketplace template does not upgrade an existing deployment.
References
Template Content
RustFS
rustfs/rustfs:1.0.6