A bit of context: LC processing normally only happens once a day, so smaller granularity for the age here couldn’t be implemented as expected. This would be tantamount to an RFE to fundamentally change the LC workflow.
On Mar 27, 2025, at 10:31 AM, Konstantin Shalygin <k0ste@k0ste.ru> wrote:
Hi,
Do you try to contact with Amazon to change lifecycle specs and add hours and minutes support? Without spec Ceph can't operate non Days field
k Sent from my iPhone
On 27 Mar 2025, at 10:50, Szabo, Istvan (Agoda) <Istvan.Szabo@agoda.com> wrote:
Hi,
Is there a way to have hourly or minute based lifecycle rather than a 1 day set on a bucket?
When I checked multiple xml rules all of them day based and can't set hour or minute value:
Multipart cleaning: <?xml version="1.0" ?> <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <ID>Incomplete Multipart Uploads</ID> <Prefix/> <Status>Enabled</Status> <AbortIncompleteMultipartUpload> <DaysAfterInitiation>1</DaysAfterInitiation> </AbortIncompleteMultipartUpload> </Rule> </LifecycleConfiguration>
Basic retention: <?xml version="1.0" ?> <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <ID>5 days retention</ID> <Prefix/> <Status>Enabled</Status> <Expiration> <Days>5</Days> </Expiration> </Rule> </LifecycleConfiguration>
Tag based retention: <?xml version="1.0" ?> <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <ID>1 day object expiry</ID> <Filter> <Tag> <Key>expiration</Key> <Value>1d</Value> </Tag> </Filter> <Status>Enabled</Status> <Expiration> <Days>1</Days> </Expiration> </Rule> </LifecycleConfiguration> Prefix based retention <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <ID>hermes-1-day-retention</ID> <Filter> <Prefix>her-</Prefix> </Filter> <Status>Enabled</Status> <Expiration> <Days>1</Days> //retention </Expiration> </Rule> </LifecycleConfiguration>
________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io