We use S3-compatible storage with a custom file provider to handle file hosting for our on-prem CMS setup.
Since MinIO switched to a source-only distribution and left the last official container with a known CVE (GHSA-jjjj-jwhf-8rgr), users who relied on the official Docker image for timely patching suddenly lost access to secure, up-to-date builds.
You can still build your own containers from source, but maintaining and patching them internally may not be a sustainable approach for many IT departments.
So, where do you go from here? We’re required to host locally (on-prem) due to legislation and internal policies, so cloud-hosted S3 is off the table.
We’ve been evaluating Garage, Cloudserver, SeaweedFS, Apache Ozone, S3Proxy, and others.
Curious — what’s your go-to MinIO alternative for on-prem S3-compatible storage?
We use S3-compatible storage with a custom file provider to handle file hosting for our on-prem CMS setup.
Since MinIO switched to a source-only distribution and left the last official container with a known CVE (GHSA-jjjj-jwhf-8rgr), users who relied on the official Docker image for timely patching suddenly lost access to secure, up-to-date builds.
You can still build your own containers from source, but maintaining and patching them internally may not be a sustainable approach for many IT departments.
So, where do you go from here?
We’re required to host locally (on-prem) due to legislation and internal policies, so cloud-hosted S3 is off the table.
We’ve been evaluating Garage, Cloudserver, SeaweedFS, Apache Ozone, S3Proxy, and others.
Curious — what’s your go-to MinIO alternative for on-prem S3-compatible storage?
References: