We recently move to S2 and our initial retention was set to 6 months. A month after the migration we decided to reduced the retention to 3 months but did not see any reduction in storage in s3.
Support found out that versioning was enabled in AWS by the PS engineer during the migration and that caused this issue.
Updated this in indexes.conf remote.s3.supports_versioning =false"
Now the new data which is rolled over is deleted but we still have old cruft remaining in s3 which is costing us heavily. Support wants us to delete the data manually by running commands from CLI.
Isnt there a better way in doing this? Does AWS lifecycle rules work only for old data which is still lying there? What are the ways to get rid of this old data apart from removing it manually.
