This section provides documentation and guidance for installing MinIO AIStor. Each subsection represents a supported platform, where guidance reflects the specific installation and configuration methods associated with that platform. If you need to install a key management service to manage cryptographic keys while objects are at rest, see the MinIO KMS docs. If you need to install DirectPV to manage container storage volumes in a Kubernetes environment, see the MinIO DirectPV docs.

MinIO AIStor Documentation MinIO AIStor is an exascale AI data store that delivers enterprise performance, scale, agi...

Configure load balancers and reverse proxies for MinIO AIStor on Linux. Includes example configurations for NGINX and HAProxy.

MinIO AIStor supports compressing objects to reduce disk usage. Objects are compressed on PUT before writing to disk, and uncompressed on GET before they are sent to the client. This makes the compression process transparent to client applications and services. Depending on the type of data, compression may also increase overall throughput. Write throughput for a production deployment is generally 500MB per second or greater per available CPU core in the system. Decompression is approximately 1 GB per second or greater for each CPU core.

The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary MinIO AIStor deployment to a bucket on a remote MinIO AIStor deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” MinIO AIStor deployment using NVMe storage to a “warm” MinIO AIStor deployment using SSD. Requirements Install and configure mc This procedure uses mc for performing operations on the MinIO AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

This procedure explains how to specify the TLS certificates your MinIO AIStor deployment requires and configure your deployment to work with the certificates. See also Enable Network Encryption for explanations of how MinIO AIStor requires TLS and which cipher suites MinIO AIStor supports. Prerequisites The appropriate X.509 certificates for your environment.

MinIO AIStor is licensed under the MinIO Software License. An active license is required for production deployments. This procedure downloads and installs the AIStor Server onto bare-metal hosts running Ubuntu Server Linux. Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. You can also open a SUBNET issue to request an architecture review or assistance during deployment. MinIO strongly recommends using only Long-Term Support (LTS) Ubuntu releases in the LTS standard security maintenance lifecycle with a Linux Kernel version 6.8 or later, such as Ubuntu 24.04 LTS. See Linux Kernel Requirements for recommended distributions and performance details.

MinIO AIStor is licensed under the MinIO Software License. An active license is required for production deployments. This page documents the installation and management of MinIO AIStor object storage using MinIO’s Red Hat OpenShift-certified operator through the Red Hat OLM. If you prefer to install on OpenShift using regular Helm charts, use the regular install instructions. This procedure assumes that the user interacting with the OpenShift cluster has authorization to:

MinIO AIStor supports deploying resources onto Windows hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of Windows. For testing or local development using a virtualized environment, including Windows Subsystem for Linux (WSL), use a machine with a higher number of cores and 16 or 32GB of RAM.

Server-Side Encryption (SSE) protects objects as part of write operations, allowing clients to take advantage of server processing power to secure objects at the storage layer (encryption-at-rest). SSE also provides key functionality for regulatory and compliance requirements around secure locking and erasure. MinIO AIStor includes support for deploying MinIO KMS as a dedicated root Key Management Service (KMS) with direct integration. MinIO KMS provides equivalent functionality to other third-party KMS solutions for managing root/external encryption keys in support of encryption operations.