MinIO AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. You must set up TLS before you can enable data encryption, also called server-side encryption. MinIO AIStor supports the following types of certificate signatures: self-signed internal or private certificate authorities (CAs) third-party CAs Multiple certificates are implemented with SNI to determine which certificate to return to a client based on the hostname in the request.

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 supports deploying resources as a container for local development and evaluation. Setting up MinIO AIStor as a container involves these steps: Deploy MinIO AIStor as a container Set up network encryption (optional) Performance The following table shows areas that have the greatest impact on MinIO AIStor performance, listed in order of importance.

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.

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 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.

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 a host running Microsoft Windows Server or Windows 11 Professional Edition. Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. Procedure Download the AIStor Server binary Invoke-WebRequest https://dl.min.io/aistor/minio/release/windows-amd64/minio -OutFile C:\minio.exe Create a data directory for use with the server The following example uses the path $HOME/minio/data. Changes this path to reflect the folder, storage volume, or drive intended for use with the server.

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 server-side bucket replication is an automatic bucket-level configuration that synchronizes objects between a source and destination bucket. MinIO AIStor server-side replication requires the source and destination bucket be two separate MinIO AIStor clusters running the same Object Store version. For each write operation to the bucket, MinIO AIStor checks all configured replication rules for the bucket and applies the matching rule with highest configured priority. MinIO AIStor synchronizes new objects and object mutations, such as new object versions or changes to object metadata. This includes metadata operations such as enabling or modifying object locking or retention settings.

The procedure on this page resynchronizes the contents of an MinIO AIStor bucket using a healthy replication remote. Resynchronization supports recovery after partial or total loss of data on an MinIO AIStor deployment in a replica configuration. For example, consider an MinIO AIStor active-active replication configuration similar to the following: Resynchronization allows using the healthy data on one of the participating MinIO AIStor deployments as the source for rebuilding the other deployment.