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.

The mc admin name command and its subcommands manage the cluster name for an AIStor deployment. The cluster name identifies the deployment in SUBNET registration and other administrative contexts. If you do not set a cluster name, AIStor automatically generates one at startup using the format <MythicalCreature><Element> (for example, “GriffinWave”, “UnicornFrost”, “KrakenStone”). The auto-generated name persists across restarts. You can also set the cluster name using the MINIO_SITE_NAME environment variable. When set with the environment variable, the name cannot be changed with mc admin name set.

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

Description The mc alias commands provide a convenient interface for managing the list of S3-compatible hosts that mc can connect to and run operations against. Subcommands mc alias includes the following subcommands:

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.

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:

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 myaistor AIStor deployment:

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:

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