Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use Management API for policy.lifecycle setting.

...

Domain Setting Values

Domain objects support a Policy-Lifecycle header to control the behavior of lifecycle policies for buckets in the domain. The header supports either of the following values:

...

Info

Lifecycle policy is not applied to unnamed content within a domain. Only named objects within buckets contains lifecycle policy applied.

Bucket Setting Values

Bucket objects support a Policy-Lifecycle header with multiple values.

...

  • For expiration days,
    Expiration time = Creation time of the current version + Number of days indicated + Rounded up to the next midnight UTC

  • For obsolete expiration days,
    Expiration time = Create time of the next newest object version + Number of days indicated + Rounded up to the next midnight UTC

  • ISO 8601 dates must unambiguously specify a calendar date. The (unspecified) expiration time is always midnight UTC of that date; any timezone specification is not allowed.

  • Expiration of a current version of an object (i.e. non-delete marker in the versioning enabled bucket) represents creating a delete marker, pushing the current version down the versioning stack.

  • In all other cases, the object or object version is permanently deleted.

...