S3 Object locking and eventual consistency?

0

Hi,

According to the S3 documentation then S3 offers eventual consistency for DELETES.
Thus you may be able to down the content of a key shortly after it has been deleted.

But, what if you set object locking on a key by using setObjectRetention.
If setObjectRetention succeeds, can it then be assumed that no delete on the key (or a versionid of they key) was in progress being propagated through out S3?

Best regards
Thomas

已提問 5 年前檢視次數 383 次
2 個答案
0

Hi Thomas,

S3 Object Lock is different from object locking in the context of consistency.

The former is an S3 feature that allows you to store objects using a write-once-read-many (WORM) model. S3 Object Lock prevent an object from being deleted or overwritten for a fixed amount of time or indefinitely. See documentation <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">here</a>. This is different from object locking in the context of consistency i.e. if two PUT requests are simultaneously made to the same key, the request with the latest time stamp wins. Amazon S3 does not currently support Object Locking. See documentation <a href ="https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html">here</a>.

Just like delete requests, Object Lock requests are also eventually consistent. As a result, an object lock request submitted at about the same time as a delete request, may not block that delete from occurring.

I hope this answers your question.

Edited by: ruhi-aws on Aug 14, 2019 10:50 AM

Edited by: ruhi-aws on Aug 14, 2019 10:51 AM

已回答 5 年前
0

Thanks for the answer.
Best regards
Thomas

已回答 5 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南