minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-05-28 00:41:14 +03:00
Code
docs/source/administration/object-management/create-lifecycle-management-expiration-rule.rst
Daryl White 6482571bf2
Update mc reference docs for improved nav structure (#717) 
- Adds landing pages for all two-word `mc` commands
- Nests three+ word commands under appropriate two-word commands
- Updates MinIO Client doc
- Uses description from each command to populate list of subcommand
descriptions
- Modifies toctree for MinIO Client doc and each command/subcommand to
improve left nav experienc

Closes #710
2023-02-02 16:52:36 -06:00

3.7 KiB
Raw Blame History

Automatic Object Expiration

minio

Table of Contents

Each procedure on this page creates a new object lifecycle management rule that expires objects on a MinIO bucket. This procedure supports use cases like removing "old" objects after a certain time period or calendar date.

Requirements

Install and Configure mc

This procedure uses mc for performing operations on the MinIO cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart <mc-install> for instructions on downloading and installing mc.

Use the mc alias set command to create an alias for the source MinIO cluster and the destination S3-compatible service. Alias creation requires specifying an access key for a user on the source and destination clusters. The specified users must have permissions <minio-lifecycle-management-create-expiry-rule-permissions> for configuring and applying expiry operations.

Required Permissions

MinIO requires the following permissions scoped to the bucket or buckets for which you are creating lifecycle management rules.

  • s3:PutLifecycleConfiguration
  • s3:GetLifecycleConfiguration

MinIO also requires the following administrative permissions on the cluster in which you are creating remote tiers for object transition lifecycle management rules:

  • admin:SetTier
  • admin:ListTier

For example, the following policy provides permission for configuring object transition lifecycle management rules on any bucket in the cluster:.

/extra/examples/LifecycleManagementAdmin.json

Expire Objects after Number of Days

Use mc ilm rule add with ~mc ilm rule add --expire-days to expire bucket contents a number of days after object creation:

mc ilm rule add ALIAS/PATH --expire-days "DAYS"
  • Replace ALIAS <mc ilm rule add ALIAS> with the alias <mc alias> of the S3-compatible host.
  • Replace PATH <mc ilm rule add ALIAS> with the path to the bucket on the S3-compatible host.
  • Replace DAYS <mc ilm rule add --expire-days> with the number of days after which to expire the object. For example, specify 30 to expire the object 30 days after creation.

Expire Versioned Objects

Use mc ilm rule add to expiring noncurrent object versions and object delete markers:

  • To expire noncurrent object versions after a specific duration in days, include ~mc ilm rule add --noncurrent-expire-days.
  • To expire delete markers for objects with no remaining versions, include ~mc ilm rule add --expire-delete-marker.
mc ilm rule add ALIAS/PATH \ 
   --noncurrent-expire-days NONCURRENT_DAYS \
   --expire-delete-marker
  • Replace ALIAS <mc ilm rule add ALIAS> with the alias <mc alias> of the S3-compatible host.
  • Replace PATH <mc ilm rule add ALIAS> with the path to the bucket on the S3-compatible host.
  • Replace NONCURRENT_DAYS <mc ilm rule add --noncurrent-expire-days> with the number of days after which to expire noncurrent object versions. For example, specify 30d to expire a version after it has been noncurrent for at least 30 days.