Returns the specified policy in JSON format if it exists on the target AIStor deployment. Syntax Example The following command returns the policy readonly in JSON format from the deployment at alias myminio.

The mc admin user enable command enables an AIStor user on the target AIStor deployment. Clients can only use enabled users to authenticate to the AIStor deployment. Users created using mc admin user add are enabled by default. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command enables user myuser on the myminio AIStor deployment:

The following procedure adds a server pool to an existing AIStor deployment running on baremetal infrastructure. Each pool expands the total available storage capacity of the cluster while maintaining the overall availability of the cluster. All commands provided below use example values. Replace these values with those appropriate for your deployment. Deploy AIStor on new hardware Follow the installation guide to install AIStor onto the new hardware. Do not start the new deployment - stop at the step Review the environment file

The mc admin cluster iam export command exports IAM metadata for use with the mc admin cluster iam import command. The command saves the output as ALIAS-iam-metadata.zip, where ALIAS is the alias of the AIStor deployment. Syntax Example The following command exports all IAM metadata for the myminio deployment.

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

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

The mc admin user command and its subcommands manage AIStor users. Clients must authenticate to the AIStor deployment with the access key and secret key associated to a user on the deployment. AIStor users constitute a key component in AIStor Identity and Access Management. To manage users who authenticate using a third-party IDP, use the command for the appropriate provider: For AD/LDAP, use mc idp ldap For OpenID Connect (OIDC) compatible providers, use mc idp openid Subcommands mc admin user includes the following subcommands:

The following procedures decommissions one or more pools on a Linux baremetal deployment. Review the AIStor deployment topology The mc admin decommission command returns a list of all pools in the AIStor deployment: mc admin decommission status myaistor The command returns output similar to the following: ┌─────┬──────────────────────────────────────────────────────────────────┬──────────────────────────────────┬────────┐ │ ID │ Pools │ Capacity │ Status │ │ 1st │ https://aistor-{01...04}.example.com:9000/mnt/disk{1...4}/aistor │ 10 TiB (used) / 10 TiB (total) │ Active │ │ 2nd │ https://aistor-{05...08}.example.com:9000/mnt/disk{1...4}/aistor │ 60 TiB (used) / 100 TiB (total) │ Active │ │ 3rd │ https://aistor-{09...12}.example.com:9000/mnt/disk{1...4}/aistor │ 40 TiB (used) / 100 TiB (total) │ Active │ └─────┴──────────────────────────────────────────────────────────────────┴──────────────────────────────────┴────────┘ The example deployment above has three pools. Each pool has four servers with four drives each.

Description The mc admin group command manages groups on an AIStor deployment. A group is a collection of users. Each group can have one or more assigned policies that explicitly list the actions and resources to which group members are allowed or denied access. Groups provide a simplified method for managing shared permissions among users with common access patterns and workloads.

Prints Prometheus metrics for a cluster. The output includes additional information about each metric, such as if its value is a counter or gauge. Syntax Example The following command prints v3 Prometheus metrics for the deployment at alias myaistor: