S3GW

S3GW is a lightweight, open-source S3-compatible object storage gateway designed for small-scale and cloud-native deployments on Kubernetes.

  • Backup
  • Cloud
  • Tools & Utilities
S3GW is a lightweight, open-source S3-compatible object storage gateway designed for small-scale and cloud-native deployments on Kubernetes.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

19/100 Low

Maintained
0last commit 964 days ago
Popular
45177 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
201 serious finding, 4 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
177
Open issues
135
Last commit
2024-03-31
Latest release
v0.23.0
License
Apache-2.0
Activity
stale

Checked today - source: GitHub (s3gw-tech/s3gw)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Installing on Kubernetes S3GW is intended for cloud-native environments and is best deployed on Kubernetes via its official Helm chart. Add the chart repository with 'helm repo add s3gw https://s3gw-tech.github.io/s3gw-charts/', then install it with 'helm install s3gw s3gw/s3gw --namespace s3gw'. The service requires an attached storage volume (any PVC or host path) to persist objects. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What does the Helm install assume about ingress and TLS?

The Helm chart assumes cert-manager and traefik are available, and you set publicDomain and ui.publicDomain. These defaults can be overridden in values.yaml.

Which ports should I expose for the Docker or Podman deployment?

Expose port 7480 for the s3gw service and port 8080 for the s3gw UI. The UI container also needs S3GW_SERVICE_URL set to the service address.

What backing storage should I use for a non-testing deployment?

Use a Kubernetes PVC or another persistent volume as the backing store. Docker and Podman runs use ephemeral container storage by default and are only for local testing.

How can I work around UI CORS issues with self-signed certificates?

First open the S3 endpoint in a browser and accept the self-signed certificate. Then access the UI via its https UI hostname.

Is s3gw suitable for Kubernetes application data backups?

It is intended for Kubernetes users who need S3-compatible object storage to back up application data to a Longhorn PV. It targets small-scale deployments rather than petabyte-scale storage.

Answers sourced from docs.s3gw.tech, docs.s3gw.tech, s3gw.tech

Community

Collected 48 days ago - public community threads