The mc version suspend command disables versioning on the specified bucket. Syntax Example The following command disables versioning for the mybucket bucket on the myaistor AIStor deployment:

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 AIStor with drives attached directly to each host node as a JBOD array with no RAID or similar management layers. 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.

MinIO announced AIStor Tables as a Technical Preview on September 30th, 2025. AIStor Tables implements native Iceberg tables support in AIStor object storage. This feature allows users to create, manage, and query Iceberg tables directly through AIStor Object Store with no dependencies on external catalog services or metadata databases. AIStor Tables implements a subset of the Iceberg REST Catalog spec functions. Applications can interact with Iceberg entities through the AIStor Iceberg API while performing S3 operations through the object storage API.

The AIStor Console is a rich graphical user interface that provides similar functionality to the mc command line tool. This page provides an overview of the AIStor Console and describes configuration options and instructions for logging in. Overview You can use the AIStor Console for administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.

AIStor supports publishing bucket notification events to a AMQP 0-9-1 service endpoint such as RabbitMQ. Prerequisites AMQP 0-9-1 service endpoint. AIStor relies on the https://github.com/streadway/amqp project for AMQP connectivity. The project is primarily tested against RabbitMQ deployments, though other AMQP 0-9-1-compatible services may also work. This procedure assumes a RabbitMQ deployment using the 0-9-1 protocol as the service endpoint.

AIStor supports publishing bucket notification events to a Kafka service endpoint. AIStor relies on the https://github.com/Shopify/sarama project for Kafka connectivity and shares that project’s Kafka support. See the sarama Compatibility and API stability section for more details. Prerequisites Kafka minimum versions and supported versions.

AIStor supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities. Steps to integrate your AD/LDAP service: Configure your AIStor cluster for AD/LDAP integration. Access the AIStor console with AD/LDAP credentials. Generate temporary credentials for application access with the AssumeRoleWithLDAPIdentity Security Token Service (STS) API See the documentation for your AD/LDAP provider for detailed information about configuring user identities. Prerequisites Access to AIStor Cluster

This page documents the steps necessary to initialize site replication between two AIStor deployments. The procedures assume at least two existing AIStor installations. Only one of the two sites can have any data at the time of setup. All other sites must be empty of buckets and objects. All sites must otherwise having the following matching configurations: AIStor Server version Key Management Server for Server-Side Encryption Identity Manager Ensure each peer site has a Load Balancer, Reverse Proxy, or similar network control plane component to handle routing connections to its AIStor Server nodes. Using a single node hostname for a peer site creates a single point of failure for site replication where replication can fail if that single node goes down.

An object is binary data, such as images, audio files, spreadsheets, or even binary executable code. The term “Binary Large Object” or “blob” is sometimes associated to object storage, although blobs can be anywhere from a few bytes to several terabytes in size. Object Storage platforms like AIStor provide dedicated tools and capabilities for storing, listing, and retrieving objects using a standard S3-compatible API. AIStor Object Storage uses buckets to organize objects. A bucket is similar to a top-level drive, folder, or directory in a filesystem (/mnt/data or C:\), where each bucket can hold an arbitrary number of objects.

AIStor supports publishing bucket notification events to a MySQL service endpoint. AIStor supports MySQL 5.7.8 and later only. Prerequisites MySQL 5.7.8 and later AIStor relies on features introduced with MySQL 5.7.8. The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.