The mc ilm rule command and its subcommands configure the rules used to transition objects between storage tiers in AIStor’s Lifecycle Management. Before creating rules with this command, use mc ilm tier and its subcommands to create the tier or tiers of other object storage locations where objects move. For more information, see the overview of lifecycle management. Subcommands mc ilm rule includes the following subcommands:

The mc replicate import command imports JSON-formatted replication rules for an AIStor bucket from STDIN. Syntax Example The following command imports the replication configuration for the mydata bucket on the myaistor AIStor deployment:

The mc replicate rm command removes a replication rule from an AIStor bucket. The mc replicate remove command has equivalent functionality to mc replicate rm. Syntax Example The following command removes the replication rule with specified id from the mydata bucket on the myaistor AIStor deployment:

The mc mv command moves an object from source to the target, such as between AIStor deployments or between buckets on the same AIStor deployment. mc mv also supports moving objects between a local filesystem and AIStor. You can also use mc mv against the local filesystem to produce similar results to the mv commandline tool. Syntax Example The following command moves objects from the mydata bucket to the archive bucket on the myaistor AIStor deployment:

The mc license info command displays information about the AIStor deployment’s license status. Syntax Example mc license info myaistor If a deployment uses an expired MinIO Commercial License, the command outputs an error message.

The mc ilm rule ls command summarizes all configured object lifecycle management rules on an AIStor bucket in a tabular format. The mc ilm rule list command has equivalent functionality to mc ilm rule ls. Syntax Example The following command lists all lifecycle management rules for the mydata bucket on the myaistor AIStor deployment:

mc idp openid accesskey edit modifies the specified access key on the local server. Example and syntax Example The following example modifies the secret for the access key mykey on the myaistor deployment:

The mc idp openid accesskey rm deletes the specified access key from the local server. mc idp openid accesskey rm is also known as mc idp openid accesskey remove. This command works against access keys created by an OIDC user after authenticating to AIStor. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithWebIdentity to generate temporary access keys using the Security Token Service.

The mc ilm tier command and its subcommands configure a remote supported S3-compatible service for AIStor Lifecycle Management: Object Transition (“Tiering”). After creating one or more tiers with this command, use mc ilm rule and its subcommands to create the rules that move objects to other storage. For more information, see the overview of lifecycle management. Subcommands mc ilm tier includes the following subcommands:

The mc idp openid accesskey ls displays a list of OIDC access key pairs. mc idp openid accesskey ls is also known as mc idp openid accesskey list. This command works against access keys created by an OIDC user after authenticating to AIStor. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithWebIdentity to generate temporary access keys using the Security Token Service.