docs/source/includes/common-minio-tiering.rst

Use the mc ilm add command to create a new transition rule for the bucket. The following tabs contain examples for transitioning objects on a calendar date or after a number of calendar days.

Transition after Calendar Date

mc ilm add ALIAS/BUCKET \
--storage-class TIERNAME \
--transition-date DATE \
--noncurrentversion-transition-date NONCURRENT_DAYS

Transition after Calendar Days

mc ilm add ALIAS/BUCKET \
--storage-class TIERNAME \
--transition-days DAYS \
--noncurrentversion-transition-days NONCURRENT_DAYS

The examples above specify the following arguments:

Argument	Description
ALIAS <mc ilm add TARGET>	Specify the alias <mc alias> of the MinIO deployment for which you are creating the lifecycle management rule.
BUCKET <mc ilm add TARGET>	Specify the full path to the bucket for which you are creating the lifecycle management rule.
TIERNAME <mc ilm add storage-class>	The remote storage tier to which MinIO transitions objects. Specify the remote storage tier name created in the previous step.
DAYS <mc ilm add transition-days>	The number of calendar days after which MinIO marks an object as eligible for transition.
DATE <mc ilm add transition-date>	The ISO-8601-formatted calendar date after which MinIO marks an object as eligible for transition.
NONCURRENT_DAYS <mc ilm add noncurrentversion-transition-days>	The number of calendar days after which MinIO marks a noncurrent object version as eligible for transition. Omit this value to ignore noncurrent object versions. This option has no effect on non-versioned buckets.

This step creates users and policies on the MinIO deployment for supporting lifecycle management operations. You can skip this step if the deployment already has users with the necessary |permissions|.

The following example uses Alpha as a placeholder alias <mc alias> for the MinIO deployment. Replace this value with the appropriate alias for the MinIO deployment on which you are configuring lifecycle management rules. Replace the password LongRandomSecretKey with a long, random, and secure secret key as per your organizations best practices for password generation.

wget -O - https://docs.min.io/minio/baremetal/examples/LifecycleManagementAdmin.json | \
mc admin policy add Alpha LifecycleAdminPolicy /dev/stdin
mc admin user add Alpha alphaLifecycleAdmin LongRandomSecretKey
mc admin policy set Alpha LifecycleAdminPolicy user=alphaLifecycleAdmin

This example assumes that the specified aliases have the necessary permissions for creating policies and users on the deployment. See minio-users and MinIO Policy Based Access Control <minio-policy> for more complete documentation on MinIO users and policies respectively.