s3 etag comparison on PutObject

Question

Is there a way to use eTags as they meant to be used with S3, where you can retrieve an object, modify it, then when you POST it back, provide the ORIGINAL etag so that your PutObject fails if someone has snuck another update in between your Get and your Put ?  I am looking to implement [optimistic updating](https://www.ibm.com/docs/en/odm/8.9.1?topic=entities-updating-retrieving-by-using-etag) as described [here](https://fideloper.com/etags-and-optimistic-concurrency-control), [here](https://event-driven.io/en/how_to_use_etag_header_for_optimistic_concurrency/), etc.  Possible?

Answer

Hi,

In S3, the PUT Object request does not have “if-match” parameter - https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
The client-side logic should handle this situation to do a comparison if the ETag is modified or not.  https://docs.aws.amazon.com/AmazonS3/latest/API/API_Object.html#API_Object_Contents

If the Objects created through PUT/POST/COPY operation or through AWS Management console that are encrypted via SSE-S3 or plaintext, the ETags are the MD5 of the object data.

s3 etag comparison on PutObject

Relevant content