1 Answers
0
Accepted Answer
http://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-set-lifecycle-configuration-intro.html says: " When you add a lifecycle configuration to a bucket, the configuration rules apply to both existing objects and objects that you add later. For example, if you add a lifecycle configuration rule today with an expiration action that causes objects with a specific prefix to expire 30 days after creation, Amazon S3 will queue for removal any existing objects that are more than 30 days old. "
http://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectVersioning.html says: " When you enable versioning on a bucket, existing objects, if any, in the bucket are unchanged: the version IDs (null), contents, and permissions remain the same. "
answered 5 years ago
Relevant questions
S3 object lock on existing S3 objects?
Accepted AnswerAmazon S3 Versioning
Accepted Answerasked 2 years agoHudi and S3 object versions
asked 6 months agoS3 Lifecycle cannot apply to S3 objects which are uploaded by unsigned requests.
asked 3 months agoS3 Bucket Object Versioning & Lifecycle Rules - Applied to Existing Objects or only New?
Accepted Answerasked 5 years agoS3 Bucket Delete Marker Policy Not Working
asked 4 months agoWhy do we need S3 bucket versioning enabled in order to do replication?
Accepted Answerasked a year agoNew to AWS, my lifecycle rule seems to not be applied (Versioned bucket)
asked 2 years agoDoes changing a s3 lifecycle policy change all older objects in an s3 bucket?
asked 3 months agoObject deletion from a non version bucket
Accepted Answerasked a month ago