The configured lifecycle rules contain multiple Expiration entries or multiple NoncurrentVersionExpiration entries with the same prefix. Before enabling the prefix overlap option, rule prefixes are not allowed to overlap.

Example

{​
    "Rules": [​
        {​
          "ID": "id",​
          "Prefix": "prefix",​
          "Status": "Enabled",​
          "Expiration": { "Days": 120 }​
        },​
        {​
          "ID": "id1",​
          "Prefix": "prefix",​
          "Status": "Enabled",​
          "Expiration": { "Days": 120 }​
        }​
    ]​
}​

The id of rule and the id1 of rule share the same prefix and both have Expiration.

Solution

It is recommended to keep only one lifecycle rule. If your actual scenario requires prefix overlapping, you can also enable the prefix overlapping feature. For detailed instructions, please refer to Enabling prefix overlap.

Last updated: 2026.10.08 17:04:03

Public security network record in Beijing: No. 11010802032137