The mc replicate ls command lists all replication rules on a AIStor bucket. Syntax Example The following command lists all enabled replication rules for the mydata bucket on the myminio AIStor deployment:

The mc ls command lists buckets and objects on a 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 myminio deployment:

The mc idp ldap accesskey ls displays a list of LDAP access key pairs. mc idp ldap accesskey ls is also known as mc idp ldap accesskey list. This command works against access keys created by an AD/LDAP user after authenticating to AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.

The mc ilm tier add command creates a new remote storage tier to a supported storage services. See Object Transition for a complete list. Syntax Example The following example creates a new remote tier called WARM-MINIO-TIER on the myminio deployment. The command creates a tier for a remote AIStor deployment located at the hostname https://warm-minio.com.

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

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 myminio 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:

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.

Overview The kes key command creates, utilizes, displays, and deletes cryptographic keys (Secrets) through the AIStor Key Encryption Service (KES). KES stores created secrets on the configured Key Management System (KMS) target. You can also use these commands to encrypt/decrypt messages or generate new data encryption keys.

Installation The following instructions install the minkms binary to your local host machine. You can use this binary for running Key Manager locally or connecting to an existing Key Manager deployment to perform management operations. Linux AMD64 curl --progress-bar --retry 10 -L https://dl.min.io/aistor/minkms/release/linux-amd64/minkms -o minkms chmod +x ./minkms mv ./minkms /usr/local/bin/ Linux ARM64 curl --progress-bar --retry 10 -L https://dl.min.io/aistor/minkms/release/linux-arm64/minkms -o minkms chmod +x ./minkms mv ./minkms /usr/local/bin/ macOS M-series (ARM64) curl --progress-bar --retry 10 -L https://dl.min.io/aistor/minkms/release/darwin-arm64/minkms -o minkms chmod +x ./minkms mv ./minkms /usr/local/bin/ Once installed, set the following environment variables to allow the minkms process to communicate with the remote Key Manager server: