Multiple NoncurrentVersionExpiration rules in the lifecycle configuration have overlapping prefixes. Before enabling the prefix overlap option, creating rules with overlapping prefixes is not allowed.

Root cause

Example

{​
    "Rules": [​
        {​
          "ID": "id",​
          "Prefix": "prefix",​
          "Status": "Enabled",​
          "NoncurrentVersionExpiration": { "NoncurrentDays": 120 }​
        },​
        {​
          "ID": "id1",​
          "Prefix": "prefix/a",​
          "Status": "Enabled",​
          "NoncurrentVersionExpiration": { "NoncurrentDays": 120 }​
        }​
    ]​
}​

Rules id and id1 have overlapping prefixes and include Expiration.

Solution

It is recommended to keep only one lifecycle rule. If lifecycle rule prefixes need to overlap in practical scenarios, you can enable the prefix overlap feature. For detailed instructions, see Enabling prefix overlap.

Last updated: 2026.10.08 17:04:03

Public security network record in Beijing: No. 11010802032137