You can enable versioning using one of the following: At bucket creation MinIO AIStor Console (WebUI) MinIO AIStor Client CLI Developers can also enable versioning on buckets through an S3-compatible SDK Enable versioning at bucket creation MinIO AIStor Console When creating a bucket in the Console, select either Versioned as the bucket Type.

MinIO AIStor bucket notifications allow administrators to send notifications to supported external services when events occur on objects or buckets, similar to Amazon S3 Event Notifications. This page lists supported event types that trigger notifications, including bucket-level and object-level S3 events. Supported notification targets MinIO AIStor supports publishing event notifications to the following targets:

This page documents upgrade procedures for AIStor Server clusters on bare-metal Linux infrastructure. All MinIO AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. Upgrade MinIO AIStor using DEB or RPM Use these steps to upgrade an MinIO AIStor cluster where the server process is managed by systemctl, such as those created using the MinIO AIStor DEB/RPM packages.

MinIO AIStor supports publishing bucket notification events to MQTT server/broker endpoint. Prerequisites MQTT 3.1 or 3.1.1 Server/Broker This procedure assumes an existing MQTT 3.1 or 3.1.1 server/broker to which the AIStor Server has connectivity. See the mqtt.org software listing for a list of MQTT-compatible server/brokers.

Configure MinIO AIStor to authenticate users with OpenID Connect providers like Okta, Keycloak, Microsoft Entra ID, or Google for SSO integration.

This page documents all requirements of bucket replication configurations, including: Active-Passive Active-Active Data Resynchronization Ensure you meet the following prerequisites before you set up any of these replication configurations. Permissions required for setting up bucket replication Bucket replication requires specific permissions on the source and destination deployments to configure and enable replication rules.

In rare circumstances, you may need to restore site replication service account information to a peer in the cluster. Seeing AccessDenied for site replication calls either in logs or with :mc-cmd:mc admin trace indicates a need to restore service account information to a peer. This error typically results when the service accounts for site replication of one of the peer sites have been lost or corrupted. Procedure To restore the required information, export the service account information from an existing healthy peer site and import it to the site with the missing account information.

The mc admin accesskey edit command modifies the configuration of an access key associated to the specified user. The command requires that at least one attribute of the access key change. Otherwise, the command exits with an error message. Syntax Example The following command applies a new policy and secret key to the myuserserviceaccount access key on the myaistor deployment:

The following procedures decommissions one or more pools on a Linux bare-metal deployment. Review the MinIO AIStor deployment topology The mc admin decommission command returns a list of all pools in the MinIO AIStor deployment: mc admin decommission status myaistor The command returns output similar to the following: ┌─────┬──────────────────────────────────────────────────────────────────┬──────────────────────────────────┬────────┐ │ ID │ Pools │ Capacity │ Status │ │ 1st │ https://aistor-{01...04}.example.com:9000/mnt/disk{1...4}/aistor │ 10 TiB (used) / 10 TiB (total) │ Active │ │ 2nd │ https://aistor-{05...08}.example.com:9000/mnt/disk{1...4}/aistor │ 60 TiB (used) / 100 TiB (total) │ Active │ │ 3rd │ https://aistor-{09...12}.example.com:9000/mnt/disk{1...4}/aistor │ 40 TiB (used) / 100 TiB (total) │ Active │ └─────┴──────────────────────────────────────────────────────────────────┴──────────────────────────────────┴────────┘ The example deployment above has three pools. Each pool has four servers with four drives each.

The mc admin cluster bucket import command imports bucket metadata as created by the mc admin cluster bucket export command. You can use this command to manually restore the metadata to the specified bucket on an MinIO AIStor deployment. If you specify only the deployment as the target, this command applies the metadata objects to all matching buckets on the target. Syntax Example The following command imports bucket metadata for the myaistor deployment from a file: