MinIO https://min.io/ provides an S3 compatible environment to act as both an object storage endpoint leveraging local disk, as well as gateway configurations brokering S3 APIs between Azure, Backblaze, Google Cloud Storage and a local disk or NAS mount-point.
See MinIO object storage endpoint on how to initialize a Filespace against your own private on-premises object storage.
In this KB we will concentrate on a NAS Gateway providing S3 Compatible API access into your Filespace. "You may run multiple MinIO instances on the same shared NAS volume as a distributed object gateway."
A Filespace utilizes the object store in a unique manner that enables random read/write streaming of your data on demand. This unique data layout breaks the data up into blocks. Each LucidLink client liaises with a local copy of metadata and draws only the blocks required, as requested.
There are certain situations where applications cannot natively access operating system file systems, as they require S3 APIs to access their data. These applications may need to collaborate with data within a Filespace therefore in order to achieve this we must overlay S3 APIs over the Filespace mount-point.
Launch MinIO as a Gateway against your Filespace mount-point, providing environment variables for your access-key and secret-keys:
set MINIO_ACCESS_KEY=abc123 set MINIO_SECRET_KEY=secret456xyz minio gateway nas L:/
Once MinIO is up and running you will be able to navigate to your endpoint:port URL and login with your environment variables access-key and secret-key.
You now have S3 compatible API access into your Filespace!
Applications that are natively written to liaise directly with object storage in Puts, Gets and API based Deletes, can now co-exist with their file system base counterparts, interacting with the same datasets, via our highly scalable, high performant distributed architecture.