Bucket lifecycle includes both expiration and transition. Amazon documentation for the feature is here:
Two different storage classes, say HDD and SSD, mapped to distinct CRUSH branches. Bucket lifecycle would transition objects from SSD to HDD after $n days. Instead of distinct CRUSH branches, the pools could be configured to use replication vs erasure coding, etc.
Filter Elements and NoncurrentVersionTransition should be supported.
Transitions can be configure per object version as well:
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.