The mc admin user add command adds a new AIStor user to the target AIStor deployment. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command creates a new user newuser on the myaistor AIStor deployment:

Description The mc admin policy commands manage policies for use with MinIO Policy-Based Access Control (PBAC). MinIO PBAC uses IAM-compatible policy JSON documents to define rules for accessing resources on an AIStor server. For complete documentation on MinIO PBAC, including policy document JSON structure and syntax, see Access Management. To manage policies for deployments that use LDAP authentication, see mc idp ldap policy.

The mc admin accesskey edit command modifies the configuration of an access key associated to the specified user. The command requires that at least one attribute of the access key change. Otherwise, the command exits with an error message. Syntax Example The following command applies a new policy and secret key to the myuserserviceaccount access key on the myaistor deployment:

AIStor supports publishing bucket notification events to MQTT server/broker endpoint. Prerequisites MQTT 3.1 or 3.1.1 Server/Broker This procedure assumes an existing MQTT 3.1 or 3.1.1 server/broker to which the AIStor Server has connectivity. See the mqtt.org software listing for a list of MQTT-compatible server/brokers.

The mc admin scanner trace command displays scanner-specific API operations occurring on the target AIStor deployment. Syntax Example The following example returns a list of API operations related to the scanner on the myaistor deployment.

You can use the AIStor Console to perform many of the deployment monitoring and management functions available in AIStor, such as: License to monitor the status and expiration of the MinIO Commercial License used for the AIStor deployment. Monitor the health and activity of the deployment by reviewing metrics, server or audit logs, trace history, S3 events, or drive health. Configure alerts by adding or managing a notification target. Set up site replication to synchronize datacenters for timely access across geographically dispersed workforces or for disaster preparedness. Configure deployment settings. Overview The Overview page displays summary information for a deployment including:

The mc admin cluster bucket import command imports bucket metadata as created by the mc admin cluster bucket export command. You can use this command to manually restore the metadata to the specified bucket on an AIStor deployment. If you specify only the deployment as the target, this command applies the metadata objects to all matching buckets on the target. Syntax Example The following command imports bucket metadata for the myaistor deployment from a file:

Required release version This command is available in AIStor Client RELEASE.2025-03-31T22-38-30Z or later. The functionality requires AIStor RELEASE.2025-03-27T23-09-45Z or later. The mc admin accesskey sts-revoke command removes security token service (sts) credentials associated with an account. Revoke all STS tokens for an account, or specify the type(s) of STS tokens to revoke for an account.

The mc alias export command exports an alias configuration from the existing configuration. The command outputs the result to STDOUT where you can either capture the output as a file or perform further modifications to the output as necessary. Syntax Example The following command exports an alias configuration from the existing host and outputs it to a file:

The mc cors remove command removes the Cross-Origin Resource Sharing (CORS) configuration from a bucket. CORS is a browser security mechanism that controls which web domains can access your object storage from client-side JavaScript. When a web application running on one domain attempts to access objects in AIStor from a different domain, the browser checks CORS policies to determine if the request should be allowed. See the Mozilla CORS documentation for more information.