MinIO AIStor supports publishing bucket notification events to a AMQP 0-9-1 service endpoint such as RabbitMQ. Prerequisites AMQP 0-9-1 service endpoint. MinIO 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.

MinIO AIStor supports publishing bucket notification events to a MySQL service endpoint. MinIO AIStor supports MySQL 5.7.8 and later only. Prerequisites MySQL 5.7.8 and later MinIO AIStor relies on features introduced with MySQL 5.7.8. 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.

The MinIO AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the MinIO AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The replicate batch job replicates objects from one MinIO AIStor deployment (the source deployment) to another MinIO AIStor deployment (the target deployment). The deployment specified as the alias becomes the ’local’ deployment for the purposes of replication.

This page documents the steps necessary to initialize site replication between two MinIO AIStor deployments. The procedures assume at least two existing MinIO 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.

The MinIO AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). Batch jobs run directly on the MinIO AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The keyrotate batch job type performs the following operations on objects in an MinIO AIStor deployment: Encrypts plaintext (unencrypted) objects using SSE-KMS. Rotates encryption keys for objects already encrypted with SSE-S3 or SSE-KMS using SSE-KMS. Rotates encryption keys for internal MinIO AIStor subsystems (IAM configuration, server configuration, tier configuration, and bucket metadata). The YAML configuration supports filters to restrict key rotation to a specific set of objects by creation date, tags, metadata, KMS key, or encryption status. You can also define retry attempts or set a notification endpoint and token.

MinIO AIStor Tables implements native Iceberg tables support in MinIO AIStor object storage. This feature allows you to create, manage, and query Iceberg tables directly through MinIO AIStor with no dependencies on external catalog services or metadata databases. MinIO AIStor Tables is compatible with Iceberg Golang, the Iceberg V3 spec, and the Iceberg REST Catalog. Applications can interact with Iceberg entities through the MinIO AIStor Iceberg API while performing S3 operations through the object storage API.

Object tiering is the moving of the data of an object from one set of hardware to another set of hardware. This is often done as a cost-saving measure, keeping more expensive and performant hardware for the newest or most accessed objects while placing other objects to less expensive and less performant storage solutions. Retrieve a tiered object When MinIO AIStor moves an object to another tier, the object’s metadata remains on the primary tier while the object’s data moves to the secondary tier. When MinIO AIStor needs to serve a tiered object, it transparently retrieves the object from the secondary tier.

MinIO AIStor brings the first native implementation of Delta Sharing to S3-compatible storage in private, public, and hybrid cloud environments.

MinIO AIStor supports publishing bucket notification events to a Kafka service endpoint. MinIO 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.

The MinIO 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 MinIO AIStor Console and describes configuration options and instructions for logging in. Overview You can use the MinIO AIStor Console for administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.