3 ms·
No, because the object may not be there (but already uploaded) with eventual consistency.
by rcaught 6y ago
No, because the object may not be there (but already uploaded) with eventual consistency.
- sterwill 6y agoBefore this update, S3 provided "read-after-write" consistency for object creation at a unique path[0] with PUT and subsequent GET operations. Replacement wasn't consistent. So I think you could have worked out some kind of atomic pattern with S3 objects, using new keys for each state change. [0] https://github.com/awsdocs/amazon-s3-developer-guide/blob/41df5c1f948b64e26d5f2583d4f97d47568a7baa/doc_source/Introduction.md#ConsistencyModel https://github.com/awsdocs/amazon-s3-developer-guide/blob/41...