This page summarizes how a DELETE operation affects objects depending on the configuration of the bucket that contains the object. Any combination of the following factors may impact how DELETE operations function: Bucket versioning Object locking rules Object Lifecycle Management rules Object tiering Site or bucket replication Scanner Permissions MinIO AIStor uses a policy based access control system for access management. The user or service account must provide the correct policy action and conditions to allow a DELETE for the bucket and object.

AIStor Server supports publishing bucket notification events to an Elasticsearch service endpoint. Prerequisites Elasticsearch v7.0 or later. MinIO AIStor relies on the v7 project for Elastic connectivity. The elastic/v7 library specifically targets Elasticsearch v7.0 and is not compatible with earlier Elasticsearch versions.

MinIO AIStor supports publishing bucket notification events to NSQ 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 an NSQ endpoint to an AIStor Server The following procedure adds a new NSQ service endpoint for supporting bucket notifications in an AIStor Server.

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 deployment to take advantage of the server-side processing power without constraints of the local machine where you run the MinIO Client. A batch file defines one job task. Once started, the MinIO AIStor server starts processing the batch job. Time to completion depends on the resources available to the deployment.

The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary MinIO AIStor deployment to a bucket on a remote MinIO AIStor deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” MinIO AIStor deployment using NVMe storage to a “warm” MinIO AIStor deployment using SSD. 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.

MinIO AIStor provides multiple replication strategies to ensure data availability, support disaster recovery, enable geographic distribution, and facilitate data migration between clusters. Each replication method serves different use cases and operates at different levels, from entire cluster to individual objects. Replication methods MinIO AIStor supports four distinct replication and synchronization approaches:

You can suspend bucket versioning at any time using the MinIO AIStor Console, the MinIO AIStor mc CLI, or using an S3-compatible SDK. Behavior While versioning is suspended, MinIO AIStor does the following in the bucket: Objects created while versioning is suspended are assigned a null version ID. Any changes to an object while versioning is suspended result in overwriting that null versioned object. MinIO AIStor does not remove or otherwise alter existing versioned objects as part of suspending versioning. Clients can continue interacting with any existing object versions in the bucket. Procedure To disable versioning, select whether you want to use the MinIO AIStor Console or the AIStor Client (mc).

MinIO AIStor provides tools for scaling your cluster capacity by adding or removing server pools. These tools allow you to expand storage capacity or retire aging hardware without disrupting ongoing operations. Planning for growth MinIO recommends initially sizing clusters for at least 2-3 years of anticipated data growth. This approach minimizes the frequency of expansion operations and simplifies long-term capacity management.

Description The mc admin cluster bucket command and its subcommands provide tools for manually importing and exporting MinIO AIStor bucket metadata. This metadata includes configurations related to features like lifecycle management rules. You can use this metadata as a snapshot of the bucket configuration for restoration later, such as part of or backup/restore operations.

Each MinIO AIStor server process exposes unauthenticated endpoints for probing server uptime and deployment high availability for simple healthchecks. These endpoints return an HTTP status code indicating whether the underlying resource is healthy or satisfies read/write quorum. The server exposes no other data through these endpoints. MinIO AIStor liveness Use the following endpoint to test if the specified MinIO AIStor server is up and ready to serve requests: