mc support upload copies a file from the local file system to a SUBNET ticket. Syntax The command has the following syntax: mc [GLOBALFLAGS] support profile \ ALIAS \ FILE \ [--comment "string"] \ [--enc] \ [--issue integer] Parameters ALIAS Required

The mc ping command performs a liveness check on a specified target. Syntax Example The following sends a response request to the target(s) and outputs the minimum, maximum, average, and roundtrip times of the response, as well as the number of errors encountered when processing the request.

The mc share download command generates a temporary presigned URL with integrated access credentials for downloading objects from an AIStor bucket. The temporary URL expires after a configurable time limit. Applications can perform a GET to retrieve the object from the URL. Users can open the URL in a browser to download the object. For more information on shareable object URLs, see the Amazon S3 documentation on Pre-Signed URLs. Syntax Example The following command generates a new presigned download URL for the mydata bucket on the myaistor AIStor deployment:

The mc mirror command synchronizes content to an AIStor deployment, similar to the rsync utility. mc mirror supports filesystems, AIStor deployments, and other S3-compatible hosts as the synchronization source. The target synchronization site file names are normalized using the shortest equivalent name. For example, s3/miniocloud//this/./object becomes miniocloud-backup/this/object. mc mirror only synchronizes the current object without any version information or metadata other than tags. To synchronize an object’s version history and other metadata, consider using mc replicate for bucket replication or mc admin replicate for site replication.

Warp Documentation Warp is an open-source testing tool for S3-compatible object storage systems. Use Warp to evaluate...

AIStor Server publishes cluster and node metrics using the Prometheus Data Model. You can use any scraping tool to pull metrics data from AIStor Server for further analysis and alerting. This page provides guidance on baseline P0 and P1 alerts for use with building alerting rules and infrastructure around the available V2 or V3 metrics. These alerts assume infrastructure similar to or exceeding our reference hardware guidelines. Modify them to reflect your needs or open a SUBNET issue for further guidance.

The 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 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 AIStor deployment (the source deployment) to another AIStor deployment (the target deployment). The deployment specified as the alias becomes the ’local’ deployment for the purposes of replication.

Configure AIStor to authenticate users against Active Directory or LDAP directory services with support for multiple providers.

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.

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.