The mc head command displays the first n lines of an object, where n is an argument specified to the command. mc head does not perform any transformation or formatting of object contents to facilitate readability. You can also use mc head against the local filesystem to produce similar results to the head command-line tool. Syntax Example The following command returns the first 10 lines of an object in the mydata bucket on the myaistor MinIO AIStor deployment:

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 MinIO 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 get command retrieves objects from an MinIO AIStor deployment or S3-compatible service to a local filesystem. mc get provides a simplified interface for downloading files compared to mc cp or mc mirror. mc get uses a one-way download function that trades efficiency for the power and complexity of the other commands. Syntax Example The following command downloads an object from the myaistor deployment to the local filesystem:

The mc idp ldap ls command lists all AD/LDAP configurations for an MinIO AIStor deployment. Syntax Example The following example lists all AD/LDAP configurations for the myaistor deployment.

The mc idp ldap accesskey create-with-login uses interactive terminal-based prompt to authenticate with the external AD/LDAP server and generate access keys for use with MinIO AIStor. Syntax Example The following example prompts the user to provide their AD/LDAP credentials. It then generates a new access key pair using the policy or policies associated with that AD/LDAP user.

The mc event rm command removes an event notification trigger from a bucket. The mc event remove command has equivalent functionality to mc event rm. Syntax Example The following command removes a configured event notifications for the specified bucket notification target for the mydata bucket on the myaistor MinIO AIStor deployment:

The mc license info command displays information about the MinIO AIStor deployment’s license status. The command shows: Organization name License plan and trial status Organization-level storage capacity limit License issue and expiration dates License ID (if available) API key (if available) When a license is expired, the expiry date displays in red to highlight the issue. For complete information about license management and renewal procedures, see Licenses. Syntax Example mc license info myaistor The command displays the license status and expiration information.

The AIStor Client mc support commands provides tools for analyzing deployment health or performance and for running diagnostics. You can also upload generated health reports for further analysis by MinIO AIStor engineering. mc support proxy set and mc support proxy remove are exceptions, as you may need to set up a proxy to complete the deployment registration. Subcommands mc support includes the following subcommands:

The mc rb command removes one or more buckets on MinIO AIStor or another S3-compatible service. To remove only the contents of a bucket, use mc rm instead. mc rb permanently deletes bucket(s) on the target deployment, including any and all object versions and bucket configurations such as lifecycle management or replication. You can also use mc rb against the local filesystem to produce similar results to the rm --rf command-line tool.

The mc idp openid update command modifies an existing set of configurations for an OIDC provider. Example and syntax Example The following example changes two of the configuration settings for the myaistor deployment as defined in the DEX configuration for Dex integration.