- Newest
- Most votes
- Most comments
Yes, that is my understanding. With versioning enabled, deletions in the file system will not remove the previously synced versions of the file store in S3 automatically. An object expiration lifecycle policy may be a helpful resource in reducing storage costs here.
If you have an object expiration lifecycle policy in your non-versioned bucket and you want to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one current and zero or more noncurrent object versions.) For more information, see How Do I Create a Lifecycle Policy for an S3 Bucket? in the Amazon Simple Storage Service Console User Guide
(https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html)
Relevant content
- Accepted Answerasked 10 months ago
- Accepted Answerasked a year ago
- asked 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago