This section provides reference documentation for AIStor Object Store components. The AIStor Server reference provides extensive details of how AIStor Server works. As you build or expand your infrastructure, look here for requirements for compute, network, memory, and storage, as well as thresholds and limits. Find recommended hardware tests, detailed explanations of how the scanner works and how to implement S3 express. AIStor provides extensive set of options to customize how AIStor runs. Configure the many options through either environment variables or configuration settings.

Creates a new policy on the target AIStor deployment. AIStor deployments include the following built-in policies by default: consoleAdmin readonly readwrite diagnostics writeonly Syntax Example Consider the following JSON policy document saved at a file called /tmp/listmybuckets.json:

The mc admin user sts info command retrieves information on the specified STS credential, such as the parent AIStor user who generated the credentials, associated policies, and expiration. Credentials provide temporary access to the AIStor deployment. Syntax Example The following command retrieves information on the STS credentials with specified access key:

The mc cors commands manage Cross-Origin Resource Sharing (CORS) configuration for buckets. Cross-Origin Resource Sharing (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.

The mc batch cancel stops an ongoing batch job. You must specify the job ID. To find the job ID, use mc batch list. Syntax Example The following command outputs the job definition for the job identified as KwSysDpxcBU9FNhGkn2dCf.

Permission This command requires that the user performing it have the admin:Rebalance policy action for the deployment. Description The mc admin rebalance command allows starts, monitors, or stops a rebalancing operation on an AIStor deployment. Rebalancing redistributes objects across all pools in the deployment.

The output is similar to what is available via journalctl -uf minio for systemd-controlled deployments. Use the mc admin logs command to show AIStor Server logs. To enable or disable the sending of logs to SUBNET for support, use mc support callhome. The uploading feature remains disabled by default until explicitly enabled for a deployment on an opt-in only basis. Syntax Example The following command displays the most recent ten server logs of any type for the alias myaistor.

Description The mc admin cluster iam command and its subcommands provide tools for manually importing and exporting AIStor identity and access management (IAM) metadata. For automatic synchronization of all IAM configurations in a deployment to a remote site, use site replication.

The mc encrypt clear command removes the current default encryption settings for a bucket. Example The following command removes the default encryption settings for the mydata bucket on the AIStor deployment associated with the myaistor alias: mc encrypt clear myaistor/mydata Syntax Syntax The command has the following syntax:

The mc idp ldap policy entities command displays a list of mappings for a user, group, and/or policy. Syntax EXAMPLE The following example lists all mappings for a specific policy, a set of groups, and a selection of users on the myaistor deployment.