Description The mc admin accesskey command and its subcommands create and manage Access Keys for internally managed users on an AIStor deployment. Each access key is linked to a user identity and inherits the policies attached to its parent user or those groups in which the parent user has membership. Each access key also supports an optional inline policy which further restricts access to a subset of actions and resources available to the parent user.

Use mc admin maintenance hosts to create lists of maintenance groups. The command generates lists of hosts that do not share erasure sets. Hosts that do not share a erasure sets can go into maintenance at the same time without causing service disruptions. Syntax The mc admin maintenance hosts command DESCRIPTION

Generates a metrics scraping configuration file for use with Prometheus. Syntax Example The following command generates a v3 Prometheus scraping configuration file for the deployment at alias myaistor:

Syntax The mc admin uncordon command returns a cordoned node to active service after maintenance. This command notifies all other nodes in the cluster that the specified node is returning to service. When you run mc admin uncordon, the command: Removes the node from the cluster’s internal list of cordoned nodes. Notifies all peer nodes that the target node is returning to service. Allows peer nodes to re-establish grid connections to the node. See Node Maintenance for a complete procedure on cordoning and uncordoning nodes.

The mc anonymous set command sets anonymous (that is, unauthenticated or public) access policies for a bucket. Buckets with anonymous policies allow clients to access the bucket contents and perform actions consistent with the specified policy without authentication. To set anonymous bucket policies using an IAM JSON policy, use the mc anonymous set-json command. Syntax Example The following command sets the anonymous access policy for the mydata bucket on the myaistor AIStor deployment:

Syntax Example The following command retrieves the JSON-formatted anonymous policy for the mydata bucket on the myaistor AIStor deployment: mc anonymous get-json myaistor/mydata Syntax The command has the following syntax:

The mc alias set command sets or updates an alias in the AIStor Client configuration. Syntax Example The following command sets an alias named myaistor:

The mc cors get command retrieves and displays the Cross-Origin Resource Sharing (CORS) configuration for a bucket in XML format. 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 idp ldap accesskey info outputs information about the specified access key(s). 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. Syntax Example The following example outputs details for the access key mykey from the myaistor deployment:

Description The mc anonymous command supports setting or removing anonymous policies to a bucket and its contents. Buckets with anonymous policies allow public access where clients can perform any action granted by the policy without authentication. Subcommands mc anonymous includes the following subcommands: