Lists the entities associated with a policy, user, or group on a target MinIO AIStor deployment. This command only returns minio-managed users and groups. To list entities associated with an Active Directory or LDAP (AD/LDAP) configuration, use mc idp ldap policy entities.

The mc admin accesskey disable command disables an existing access key for a MinIO IDP user. Syntax Example The following command disables the specified access key:

The mc admin accesskey info command returns a description of the specified access key(s). The description output includes the following details, as available: Access Key Parent user of the specified access key Access key status (on or off) Policy or policies Comment Expiration Syntax Example The following command returns information on the specified access key:

Cordon is not always necessary AIStor will correctly remove offline nodes from the cluster automatically. There are normally no additional steps required when taking a node offline for maintenance: just stop the service, perform maintenance and then restart it. For users with certain special requirements, we offer node cordoning as an option. 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.

Description The mc admin accesskey command and its subcommands create and manage Access Keys for internally managed users on an MinIO 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.

The mc admin kms key command performs cryptographic key management operations through the MinIO AIStor Key Encryption Service (KES). Syntax mc admin kms key create Creates a new master key on a Key Management System (KMS).

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.

Generates a metrics scraping configuration file for use with Prometheus. The bearer token in the generated configuration is signed locally using the credentials of the specified alias. AIStor Server uses that access key as the identity for the scrape request and requires it to have the admin:Prometheus action. For least-privilege scraping, point this command at an alias configured with a dedicated access key whose inline policy grants only admin:Prometheus. See Create a dedicated access key for Prometheus.

The mc admin accesskey ls command lists users, access keys, or temporary security token service keys managed by the MinIO AIStor deployment. You can use mc admin accesskey ls as an alias to this command. Syntax Example The following command lists all access keys associated to the user with username admin1 on the deployment at alias myaistor:

Description The mc admin policy commands manage policies for use with MinIO Policy-Based Access Control (PBAC). MinIO PBAC uses IAM-compatible policy JSON documents to define rules for accessing resources on an MinIO AIStor server. For complete documentation on MinIO PBAC, including policy document JSON structure and syntax, see Access Management. To manage policies for deployments that use LDAP authentication, see mc idp ldap policy.