The mc retention info command configures the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also set the default object lock settings for a bucket, where all objects without explicit object lock settings inherit the bucket default. To lock an object under legal hold, use mc legalhold set. mc retention info requires that the specified bucket has object locking enabled. You can only enable object locking at bucket creation. See mc mb --with-lock for documentation on creating buckets with object locking enabled.

Description The mc encrypt commands set, update, or disable the default bucket Server-Side Encryption (SSE) mode. AIStor automatically encrypts objects using the specified SSE mode. Subcommands mc encrypt includes the following subcommands:

Description The mc idp ldap commands allow you to manage configurations to 3rd party Active Directory or LDAP Identity and Access Management (IAM) integrations. The mc idp ldap commands are an alternative to using environment variables when setting up an AD/LDAP connection. They are only supported against AIStor deployments. See Active Directory / LDAP Access Management for a tutorial on using these commands.

The mc idp ldap enable command enables the AD/LDAP IDP server configuration for an AIStor deployment. Syntax Example The following example enables the AD/LDAP configuration for the myminio deployment.

The mc support inspect command collects the data and metadata associated to objects at the specified path. If this information is required to diagnose a AIStor SUBNET issue, AIStor Engineering will provide the appropriate command. AIStor assembles this data from each backend drive storing an erasure shard for each specified object. For registered clusters, the file uploads to AIStor for use by the engineering team in support efforts.

The mc idp ldap policy detach command detaches one or more polices from an entity. Syntax Example The following example detaches the policy userpolicy from the user bobfisher on the myminio deployment.

Use the mc support proxy command to configure a proxy to use to communicate with AIStor SUBNET. Syntax mc support proxy set Create a proxy URL for the AIStor deployment to use when communicating with AIStor SUBNET.

The mc ready command checks the status of a cluster and whether the cluster has read and write quorum. Example The following sends a GET request to the cluster at alias myminio and returns its status. mc ready myminio The command sends a GET request to the deployment at the alias myminio.’ The command repeats the request until it is successful.

The mc replicate export command exports the JSON-formatted replication rules for an AIStor bucket to STDOUT. Syntax Example The following command exports the replication configuration for the mydata bucket on the myminio AIStor deployment:

AIStor supports deploying resources onto macOS hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of macOS. For testing or local development using a virtualized environment, use a machine with a higher number of cores and 16 or 32GB of RAM.