Hi Yes, Ozone supports STS, that's why I mentioned it. It's probably close enough to minIO (even if some "adaptation" might be required for STS).
Just my $0.01 Regards JB On Fri, Jan 9, 2026 at 2:15 AM Yufei Gu <[email protected]> wrote: > Agreed with Dmitri that STS is essential in this case, otherwise a local > file system will be good enough. > > AFAIK, Apache Ozone supports STS starting from 2.1.0, > https://ozone.apache.org/release/2.1.0/. > > Yufei > > > On Thu, Jan 8, 2026 at 4:55 PM Dmitri Bourlatchkov <[email protected]> > wrote: > > > Hi François, > > > > I could not find any mention of STS / AssumeRole in GarageHQ docs (really > > quick looks), so I assume it does not support STS... Do you know for > sure? > > > > STS is pretty important for ease of use in Polaris getting started (i.e. > > setup without STS is more involved). > > > > Cheers, > > Dmitri. > > > > On Thu, Jan 8, 2026 at 3:09 PM Francois Papon <[email protected]> wrote: > > > > > Hi, > > > > > > About other solutions, I made some test to evaluate GaragHQ as an > > > alternative to MinIO: > > > > > > https://garagehq.deuxfleurs.fr/ > > > > > > I don't know if all the required functionnalities used by Polaris are > > > provided but for the test/quickstart part may be it can do the job. > > > > > > regards, > > > > > > François > > > > > > Le 08/01/2026 à 16:35, Adam Christian a écrit : > > > > Thanks, folks! Great points! I do like the idea of using something > > other > > > > than MinIO. > > > > > > > > My only 2 cents: For the quickstart docker compose file, I believe > that > > > we > > > > should use object storage that can be automatically configured > without > > > > having to put in credentials. The goal of the quickstart is to have > > > anyone > > > > who has Docker running locally to be able to launch a non-production > > > > version of Polaris through a single command. It's targeted for users > > who > > > > are just learning about Polaris. So, in my opinion, this rules out > AWS > > > S3. > > > > > > > > As long as we meet that criteria, I do think that changing would be > > > > appropriate. Thanks for bringing this up! > > > > > > > > Go community, > > > > > > > > Adam > > > > > > > > On Thu, Jan 8, 2026 at 9:16 AM Dmitri Bourlatchkov < > > > > [email protected]> wrote: > > > > > > > >> Hi All, > > > >> > > > >> Apache Ozone works well, AFAIK [1] but it certainly requires more > > setup > > > >> work than MinIO. > > > >> > > > >> WDYT about RustFS? [2] > > > >> > > > >> [1] > > > >> > > > >> > > > > > > https://polaris.apache.org/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-ozone/ > > > >> > > > >> [2] https://github.com/rustfs/rustfs > > > >> > > > >> Cheers, > > > >> Dmitri. > > > >> > > > >> On Thu, Jan 8, 2026 at 8:46 AM Jean-Baptiste Onofré < > [email protected]> > > > >> wrote: > > > >> > > > >>> Hi Yong, > > > >>> > > > >>> Thanks for bringing this to our attention. > > > >>> > > > >>> I agree with your assessment regarding the recent changes to MinIO > > OSS. > > > >> We > > > >>> could evaluate Apache Ozone as a potential alternative; while STS > > might > > > >>> require more changes, I believe it’s worth investigating. > > > >>> > > > >>> In the short term, we could update the quickstart guide to use AWS > S3 > > > >> while > > > >>> we wait to finalize the Ozone integration. > > > >>> About Ceph, that's a good idea, assuming we have the same kind of > > > >>> layout/experience. > > > >>> > > > >>> Regards, > > > >>> JB > > > >>> > > > >>> On Thu, Jan 8, 2026 at 7:49 AM Yong Zheng <[email protected]> > wrote: > > > >>> > > > >>>> Hello, > > > >>>> > > > >>>> We have MinIO support as S3 compatible storage and this is great > as > > it > > > >>>> allows users to quickly test out Apache Polaris as a catalog and > > write > > > >>> to a > > > >>>> S3 compatible storage. However, as MinIO is now under maintenance > > mode > > > >>> only > > > >>>> for OSS (https://github.com/minio/minio?tab=readme-ov-file), we > > won't > > > >> be > > > >>>> able to get updated images from public image registry, should we > > > >> consider > > > >>>> switch our primary getting-start example to non-MinIO one instead > > (the > > > >>>> current one is MinIO as backend: > > > >>>> > > > >> > > > > > > https://github.com/apache/polaris/blob/main/getting-started/quickstart/docker-compose.yml > > > >>> )? > > > >>>> Without doing so, users will be likely pulling down outdated MinIO > > > >> images > > > >>>> with critical CVEs couple months later for their local setup to > play > > > >>>> around. If using outdated MinIO is a concern as the getting-start > > > >>> example, > > > >>>> maybe we should switch to the Ceph one ( > > > >>>> > > > >> > > > > > > https://github.com/apache/polaris/blob/main/getting-started/ceph/docker-compose.yml > > > >>> ) > > > >>>> but updated it to match the same layout? > > > >>>> > > > >>>> Thanks, > > > >>>> Yong Zheng > > > >>>> > > > > > >
