The mc replicate update command modifies an existing bucket replication rule. Syntax Example The following command modifies an existing replication rule for the mydata bucket on the myaistor MinIO AIStor deployment:

The mc qos rule import command imports a Quality of Service (QoS) configuration to an MinIO AIStor deployment from a YAML file. The command reads the YAML configuration from standard input (STDIN). For more information, see Bucket-level Quality of Service. Syntax Example The following command imports the QoS configuration from a file named qos.yaml to the mybucket bucket on the myaistor deployment:

The mc ilm restore command creates a temporary copy of an object archived on a remote tier. The copy automatically expires after 1 day by default. Syntax Use this command to allow applications to access a tiered object through the MinIO AIStor deployment (that is, the “hot tier”). The archived object remains on the remote tier, while the temporary copy becomes HEAD for that object.

The mc ilm tier check command displays the configuration for remote tier on a deployment. Syntax Example The following example displays the configuration for an existing remote tier called WARM-TIER on the myaistor deployment.

The mc idp openid accesskey info outputs information about the specified access key(s). This command works against access keys created by an OIDC user after authenticating to MinIO AIStor. Authenticated users can manage their own long-term Access Keys using the MinIO AIStor Console. MinIO AIStor supports using AssumeRoleWithWebIdentity to generate temporary access keys using the Security Token Service. Example and syntax Example The following example outputs details for the access key mykey from the myaistor deployment:

The mc ilm rule import command imports an object lifecycle management configuration and applies it to an MinIO AIStor bucket. The mc ilm rule import command imports from STDIN by default. You can input the contents from a .json file, such as one produced by mc ilm rule export. The following command imports the lifecycle management configuration from mydata-lifecycle-config.json and applies it to the mydata bucket on the myaistor deployment:

Remove an existing set of configurations for an OIDC provider. Example and syntax Example The following example removes the oidc-config settings for the myaistor deployment.

The mc ilm rule rm command removes an object lifecycle management rule from an MinIO AIStor Bucket. Example The following command removes a single lifecycle management rule from the mydata bucket on the myaistor MinIO AIStor deployment: mc ilm rule rm --id "bgrt1ghju" myaistor/mydata Syntax The command has the following syntax:

The mc idp openid info command outputs the configuration for a specified OIDC provider on a specified MinIO AIStor deployment. Optionally validates the configuration with the --check flag. Example and syntax Example The following example outputs the configuration settings defined for the test_config set of OIDC settings on the myaistor deployment and adds the optional --check flag to report whether the configuration is valid.

The mc qos rule add command adds a single new Quality of Service (QoS) rule to an MinIO AIStor deployment. For more information, see Bucket-level Quality of Service. Syntax Example The following command adds a QoS rule to limit the s3.GetObject API to 100 requests per second for the bucket1 bucket: