The mc ilm tier ls command shows the remote tiers configured on a deployment. The mc ilm tier list command has equivalent functionality to mc ilm tier ls. Syntax Example The following example outputs a list of the existing remote tiers on the myaistor deployment.

Syntax The mc ilm rule export command exports the object lifecycle management configuration for an AIStor bucket. The mc ilm rule export command outputs to STDOUT by default. You can output the contents to a .json file for archival or ingestion using mc ilm rule import.

The mc license register command connects your deployment with your MinIO SUBNET account. The registration process collects the following information about the cluster for upload to SUBNET: Deployment ID Cluster Name Used capacity AIStor Object Store version Number of server pools Number of servers Number of drives Total space across all drives Space used across all drives Number of buckets Number of objects After registration, you can upload deployment health reports directly to SUBNET using the mc support diag command.

The mc undo command reverses changes due to either a PUT or DELETE operation at a specified path. Syntax Example The following command reverts the last three uploads and/or deletions of the file.zip object on the myaistor deployment in the data bucket:

The following section documents settings for configuring AIStor to publish minio server logs to an HTTP webhook endpoint. See Publish Server Logs to HTTP Webhook for more complete documentation and tutorials on using these settings. Example Environment Variables You can specify multiple webhook endpoints as log targets by appending a unique identifier _ID for each set of related logging environment variables. For example, the following settings define two distinct server log webhook endpoints:

The following section documents environment variables for configuring AIStor to publish audit logs to an HTTP webhook endpoint. See Publish Audit Logs to HTTP Webhook for more complete documentation and tutorials on using these environment variables. Example Environment Variables You can specify multiple webhook endpoints as audit log targets by appending a unique identifier _ID for each set of related logging settings.

This page covers settings that manage access and behavior for the AIStor Console. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

This page documents settings for configuring an MQTT service as a target for Bucket Notifications. See Publish Events to MQTT for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

This page covers settings that control root (superuser) access for the AIStor process. The root user has complete access and permissions to perform operations on the AIStor deployment. Root User and Root Password are required even if you use the MinIO Key Encryption Service or other key management utility. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

1. Constructor Minio(endpoint, access_key=None, secret_key=None, session_token=None, secure=True, region=None, http_client=None, credentials=None) Initializes a new client object.