The AIStor Server process stores its configuration in the storage backend directory. These settings define runtime behavior of the AIStor Server process. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

The mc table view show command displays metadata for an Iceberg view on an MinIO AIStor cluster. The output includes the view schema, SQL definition, and properties. Example The following command displays metadata for the monthly_sales view in the prod namespace of the analytics warehouse on the myaistor MinIO AIStor cluster:

The mc support perf object command measures the S3 performance of reading and writing objects in a cluster. MinIO AIStor autotunes concurrency to obtain maximum throughput and IOPS (Input/Output Per Second). The command displays results in a terminal user interface (TUI) with a spinner during testing and a tabular output showing per-server PUT and GET performance statistics. Use this command to identify potential S3 API performance bottlenecks in your deployment.

The following page includes the full contents of the MinIO AIStor Custom Resource Definition V1 (Stable) CustomResourceDefinition. API Reference Packages aistor.min.io/v1 aistor.min.io/v1 Package v1 - This page provides a quick automatically generated reference for the MinIO AIStor ObjectStore Operator aistor.min.io/v1 CRD.

Generate temporary S3 credentials using Active Directory or LDAP user credentials with the MinIO AIStor STS AssumeRoleWithLDAPIdentity API.

This page provides an example that shows how to create an MinIO AIStor Tables warehouse and perform basic table operations with the AIStor Client and PyIceberg, a lightweight Python API for interacting with Iceberg Tables. You use the client to create the needed resources and Python code to insert and query data using the MinIO AIStor Tables API. You can also call the MinIO AIStor Tables API directly, instead of working with the MinIO AIStor client commands. See the MinIO AIStor Tables API Reference for more information.

MinIO AIStor implements an S3 extension to perform READ actions like download, list, or get metadata for individual files inside a ZIP archive stored in a bucket. S3 requests can return information for individual files within the ZIP archive, including file size and custom headers. To access ZIP archive contents, do the following: Set the x-minio-extract header to true in your S3 requests. Append the path of the content inside the archive to the path of the archive itself. For example, to download 2025/taxes.csv archived in financial.zip and stored under a bucket named company-data, issue a GET request using the path:

The MinIO Go Client SDK provides straightforward APIs to access any Amazon S3 compatible object storage. This Quickstart Guide covers how to install the MinIO client SDK, connect to MinIO, and create a sample file uploader. For a complete list of APIs and examples, see the godoc documentation or Go Client API Reference. These examples presume a working Go development environment and the MinIO mc command line tool. Download from GitHub From your project directory:

MinIO AIStor supports running in S3 Express Mode, an AWS S3 API surface for ultra-low latency, single-zone storage. This mode enables directory bucket behavior for optimized hierarchical storage structures, implementing the specific directory bucket behaviors documented by AWS. Enable S3 Express mode Add the --api parameter to the MINIO_OPTS parameter list in /etc/default/minio:

Drive type MinIO recommends using flash-based storage (NVMe or SSD) for all workload types at any scale. Workloads that require high performance should prefer NVMe over SSD. For best performance, use 30+TB drives with NVMe over PCIe 4.0 or 5.0. Directly attached storage For best performance, provide MinIO AIStor with drives attached directly to each host node as a JBOD array with no RAID or similar management layers. MinIO AIStor requires the XFS filesystem for best performance and behavior at scale. Using any other type of backing storage (SAN/NAS, ext4, RAID, LVM) typically results in a reduction in performance, reliability, predictability, and consistency.