Articles in this section

lifecyclerule modify

Sara Levy
Follow

This command modifies an S3 lifecycle rule.

Usage
lifecyclerule modify --name NAME
              [--enable|--disable]
              [--prefix PREFIX]   
              [--min-size SIZE]
              [--max-size SIZE]
              [--expiration-days DAYS]
              [--enable-expired-obj-delete-marker|--disable-expired-obj-delete-marker]
              [--noncurrent-days DAYS]
              [--newer-noncurrent-versions VERSIONS]
              [--abort-mpu-days-after-initiation DAYS]
Required Parameters

--id ID

Specifies which to modify.
Options

--enable

Enables the rule.

--disable

Disables the rule.

--prefix PREFIX

Specifies a prefix common to limit the object scope by object prefix.

For example: --prefix logs/

--min-size SIZE

Specifies a minimum object size to limit the scope by size.

Specify SIZE as an integer followed by MB, GB, TB, etc.

For example: --min-size 2GB

--max-size SIZE

Specifies a maximum object size to limit the scope by size.

Specify SIZE as an integer followed by MB, GB, TB, etc.

For example: --max-size 1TB

--expiration-days DAYS

Specifies a number of days after objects are created that they expire.

In a non versioned bucket view, expiration means that the object is permanently removed.

In a versioned bucket view, where the objects are versioned:

  • if the current version is not a delete marker, a delete marker is created and that becomes the current version. The existing current version is retained as a non current version. When the delete marker reaches this same number of days, it is deleted.

  • If there are one or more object versions and the delete marker is the current version, no action is taken.

  • If the current object version is the only object version and it is also a delete marker, it is removed. That is, all object versions were deleted and there is only a delete marker remaining. This is called an expired object delete marker and it is removed.

--enable-expired-obj-delete-marker

Relevant only for versioned buckets.

Enables deletion of expired object delete markers when they become expired object delete markers.

An expired object delete marker is an object version that is the only version of an object and is also a delete marker.

This parameter is mutually exclusive with --expiration-days DAYS, which deletes expired object delete markers when they satisfy the specified age criteria. If you want to expire objects using --expiration-days DAYS and also clean up expired object delete markers as soon as they are created as such, create two separate rules.

--disable-expired-obj-delete-marker

Relevant only for versioned buckets.

Disables deletion of expired object delete markers when they become expired object delete markers.

--noncurrent-days DAYS

Relevant only for versioned buckets. If provided, noncurrent versions of objects are deleted after the specified number of days, provided they are not the newest noncurrent versions up to the number set to be retained, if that number is provided with --newer-noncurrent-versions VERSIONS.

--newer-noncurrent-versions VERSIONS

Relevant only for versioned buckets. Use this parameter to specify a number of noncurrent versions of objects to retain. The newest non current versions up to this number will not expire even if they exceed --noncurrent-days .

--abort-mpu-days-after-initiation DAYS

Specifies to remove incomplete multipart uploads, which are not removed through --expiration-days. The value is the number of days after multipart uploads are started when they should be aborted and removed if they are incomplete.

Related articles

Comments

0 comments

Article is closed for comments.