This page covers settings that manage access and behavior for the batch job process. 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.

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 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 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.

The mc ls command lists buckets and objects on an AIStor deployment. You can also use mc ls to list objects on S3-compatible services. Syntax Example The following command lists all objects in a bucket on the myaistor deployment:

The mc put command uploads objects from a local filesystem to an AIStor deployment. You can also use mc put to upload objects to S3-compatible services. Syntax Example The following command uploads a file from the local filesystem to the myaistor deployment:

The mc legalhold info command returns the current legal hold setting for an object or objects. mc legalhold requires that the specified bucket has object locking enabled. You can enable object locking at bucket creation. See mc mb --with-lock for documentation on creating buckets with object locking enabled. Version changed Beginning with RELEASE.2025-05-20T20-30-00Z, AIStor allows setting object locking and retention rules on any existing bucket. Earlier versions of AIStor only allowed setting retention rules for buckets at the bucket’s creation.

This section documents settings that control behavior related to AIStor metrics and logging. See Metrics and Alerts for more information. 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.

The mc support top disk command displays current drive statistics. Syntax Example The following command displays the current disk usage and performance on the alias myaistor.

The mc share ls command displays any unexpired presigned URLs generated by mc share upload or mc share download. The mc share list command has equivalent functionality to mc share ls. Applications can perform a PUT to retrieve the object from the URL. For more information on shareable object URLs, see the Amazon S3 documentation on Pre-Signed URLs. Syntax Example The following command lists all upload and download presigned URLs respectively for the mydata bucket on the myaistor AIStor deployment: