Why is my S3 lifecycle configuration isn't working as expected?

Question

Hi,

I have a versioned bucket where I want deleted and other non-current objects to be moved to Glacier after some period of time. I configured a bucket policy that should move non-current versions after 1 day to test this:
```
{
    "Rules": [
        {
            "ID": "Move deleted to Glacier",
            "Filter": {},
            "Status": "Enabled",
            "NoncurrentVersionTransitions": [
                {
                    "NoncurrentDays": 1,
                    "StorageClass": "GLACIER_IR"
                }
            ]
        }
    ]
}
```
![Enter image description here](https://repost.aws/media/postImages/original/IMfCiYS3NZRbm3WGhBbbwx2A)

But the object is still there with the "Standard" storage class more than 10 days after it was deleted:

![Enter image description here](https://repost.aws/media/postImages/original/IM-8FTItHcRB2GfiNPbDGoyw)

Why is this, and how can I move all non-current and deleted objects to another storage class (Glacier)?

VISI · Answer

Thanks for posting.
First, a "Delete" marker is a placeholder for a versioned file in the "s3" bucket, and it will only allow performing the "Delete" action into this. Because "Delete" marked files or objects are not coupled with any data or access control list (ACL) value. 
Furthermore, it cannot retrieve anything from "GET" requests due to free for any data association. and even cant performed any API calls except "Delete".

As per definition, the only action that can be performed is "Delete", Therefore "Delete" markers will not be able to transition or move from the standard bucket to any other storage class bucket or vice-versa.

Why is my S3 lifecycle configuration isn't working as expected?

回答を追加する

関連するコンテンツ