2 Answers
- Newest
- Most votes
- Most comments
0
S3 Natively does not have any conditions that would satisfy this for the PutObject but what you could consider is making a HeadObject request first and if the object does not exist (404 - requires the writer to have s3:ListBucket permission) then continue with the PutObject.
0
Set an object lock https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html
answered 9 months ago
Relevant content
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 7 months ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago
This is a check-then-act race condition.