Within the same lifecycle rule, or multiple rules with overlapping prefixes, there is a time conflict between NoncurrentVersionExpiration and NoncurrentVersionTransition settings (for example, set to delete after 20 days and transition to archive after 30 days).

Root cause

TOS requires that the days to transition between storage types must follow this order:

Infrequent Access < Intelligent Tiering < Flashback Archive < Archive < Cold Archive < Deep Cold Archive < Deletion after expiration

Example

The following rule configures historical version objects to delete after 10 days and transition to infrequent access after 30 days, which does not meet the requirements.

{​
    "Rules": [{​
      "ID": "id",​
      "Prefix": "prefix",​
      "Status": "Enabled",​
      "NoncurrentVersionExpiration": { "NoncurrentDays": 10 },​
      "NoncurrentVersionTransition": [​
        {​
          "StorageClass": "IA",​
          "NoncurrentDays": 30​
        }​
      ]​
    }]​
}​

Solution

When configuring NoncurrentVersionExpiration and NoncurrentVersionTransition simultaneously, the number of days for transitioning to different storage types must follow this order:

Infrequent Access < Intelligent Tiering < Flashback Archive < Archive < Cold Archive < Deep Cold Archive < Deletion after expiration

Last updated: 2026.07.28 10:13:31

Public security network record in Beijing: No. 11010802032137