By using AWS re:Post, you agree to the Terms of Use
/Does a transition rule create versioned objects?/

Does a transition rule create versioned objects?

0

I have a versioned bucket with a transition rule to Deep Glacier. The original (at upload) storage class was Standard-IA and after some time (transition rule was applied) I found the transitioned objects as current version with storage class Deep Glacier (as intended) but additionally the originally uploaded objects (as previous version) with their original storage class (Standard-IA).
What would cause that behaviour?
I was under the impression, that storage class transitions (both manual and lifecycle-based) just modify the objects storage class but don't replicate it into multiple versions. True?

asked 2 years ago0 views
3 Answers
0

When you specify a lifecycle policy there are options for the current version and the previous version. Have you also applied your existing policy to previous versions?

answered 2 years ago
0

I'm aware that a policy can or can not include existing "old" versions. The policy is set only to apply to the current version.
But there was only ever one version created (by me), a single upload to the object no modifications thereafter. Only after some time, the "old" versions appeared additionally, assumingly created by the policy. An accidental (unintended) re-upload is unlikely, as it involved +500Gbyte that would have needed a couple of days to upload.

answered 2 years ago
0

Lifecycle rules do not create a new version of the object. If you have CloudTrail enabled, I recommend looking at your request history to identify what created the second version. That second version would have been created before the lifecycle rule moved the objects to Glacier.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions