Can we do write-object-if-not-exist in S3 similar to conditional put in Dynamo DB?

Question

I have a use case, where I need to avoid overriding the objects. I do understand that because of the distributed nature of the S3, it might not available. Are there any tricks and hacky way to achieve not to override the object in S3 ?

Dynamo DB is also distributed, but it provides conditional put. Wondering what is the architectural difference between Dynamo DB and S3 ?

Kit - CostCenter · Answer

Set an object lock https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html

AWS-User-1378901 · Answer

Now it's a released feature of S3: https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3-conditional-writes/

Suran_N · Answer

S3 Natively does not have any conditions that would satisfy this for the [PutObject](https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html) but what you could consider is making a [HeadObject](https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html) request first and if the object does not exist (404 - requires the writer to have s3:ListBucket permission) then continue with the PutObject.

Can we do write-object-if-not-exist in S3 similar to conditional put in Dynamo DB?

Add your answer

Relevant content