MinIO AIStor uses Policy-Based Access Control (PBAC) to define the authorized actions and resources to which an authenticated user has access. Each policy describes one or more actions and conditions that outline the permissions of a user or group of users. MinIO AIStor PBAC is built for compatibility with AWS IAM policy syntax, structure, and behavior. This documentation makes a best-effort to cover IAM-specific behavior and functionality. Refer also to the AWS IAM documentation for more information.

MinIO AIStor Table Shares support grouping multiple tables under a single share. Each share has one or more schema under which you can associate multiple tables. When you access the share from a remote client, you can perform operations against any table under a given schema. When you create a new table share, you define the initial schema and table associated to that share. You can then add new tables to that share under the same or a different schema.

If an MinIO AIStor node suffers complete hardware failure (for example, loss of all drives, data, etc.), the node begins healing operations once it rejoins the deployment. MinIO AIStor healing occurs only on the replaced hardware and does not typically impact deployment performance. MinIO AIStor healing ensures consistency and correctness of all data restored onto the drive. Changed in RELEASE.2025-02-04T00-52-01Z If multiple drives within the same erasure set require healing, MinIO AIStor prioritizes the first drive that begins healing within the erasure set. Other drives in the erasure set wait until healing finishes on the first drive before the next drive starts healing.

MinIO AIStor supports publishing bucket notification events to a Redis service endpoint. Prerequisites The MinIO AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a Redis endpoint to an AIStor Server The following procedure adds a new Redis service endpoint for supporting bucket notifications in an AIStor Server.

The procedure on this page creates a new object lifecycle management rule that transition objects from an MinIO AIStor bucket to a remote storage tier on the storage backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date. 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.

Upgrade MinIO to MinIO AIStor in airgapped Kubernetes environments using private registries, mirrored images, and custom service registry configurations.

This page provides an overview of AIStor Server deployment architectures from a production perspective. A production AIStor Server deployment consists of at least 4 hosts with homogeneous storage and compute resources. Each AIStor Server host in this pool has matching compute, storage, and network configurations These hosts make up a server pool, where the AIStor Server presents the aggregated compute, memory, and storage as a single resource to clients. Each pool consists of one or more erasure sets.

This page describes how to upgrade MinIO AIStor Helm clusters that use a private container registry but have internet access to helm.min.io for chart updates. If your cluster uses public registries or is in an airgapped environment, see: Upgrade with Public Registries Upgrade in Airgapped Environment Overview MinIO AIStor Helm upgrades involve updating two components:

AIStor Server implements Erasure Coding as a core component in providing data redundancy and availability. The diagrams and content in this section present a simplified view of erasure coding operations and are not intended to represent the complexities of the AIStor Server’s full erasure coding implementation. MinIO AIStor groups drives in each server pool into one or more Erasure Sets of the same size. By default, each erasure set can contain 2 to 16 drives. You can configure erasure sets up to 32 drives with the MINIO_ERASURE_SET_DRIVE_COUNT environment variable if running AIStor Server RELEASE.2026-02-02T23-40-11Z or later.

Troubleshoot common upgrade issues including KES certificates, PolicyBinding errors, OperatorHub subpath problems, and object store failures.