Description The mc admin config command manages configuration settings for the AIStor Server. Examples Syntax mc admin config set Sets a configuration key on the AIStor deployment. Configurations defined by environment variables override configurations defined by this command.

Attaches one or more IAM policies to either an AIStor-managed user or a group. Exactly one --user or one --group is required. This command is intended for managing policy associations for MinIO-managed users only. For attaching policies to OpenID-managed users, see OpenID Connect Access Management.

The mc encrypt set encrypt command sets or updates the default bucket Server-Side Encryption (SSE) mode. AIStor automatically encrypts objects written to that bucket using the specified SSE mode. mc encrypt set supports only SSE-KMS and SSE-S3 encryption types. Syntax Example The following command sets the default encryption configuration for a bucket:

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:

Syntax The mc admin cordon command removes a node from active service for maintenance purposes. By default, the command initiates a graceful drain before fully cordoning the node, allowing existing client connections to complete before the node goes offline. Once cordoned, a node:

The mc diff mc computes the differences between two filesystem directories or AIStor buckets. mc diff lists only those objects which are missing or which differ in size. mc diff does not compare the contents of objects. Syntax Example The following command computes the difference between the contents in the mydata folder on a local filesystem and the contents in the mydata bucket on the myaistor AIStor deployment:

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.

Syntax Example The following command applies the JSON-formatted anonymous policy to the mydata bucket on the myaistor AIStor deployment: mc anonymous set-json ~/mydata-anonymous.json myaistor/mydata Syntax The command has the following syntax:

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:

This tutorial shows how to setup a KES server that uses Google Cloud Secret Manager as a persistent key store. K E S C l i e n t K E S S e r v e r G o o g l e C l o u d S e c r e t M a n a g e r Google Cloud Secret Manager The Google Cloud Secret Manager is a key-value store for secrets, such as passwords, access tokens, and cryptographic keys.