1 Answers
0
Accepted Answer
Delete markers are an object and charged like any other object regardless of the bucket status(as mentioned in the documentation, size of a delete marker is euqal to its key name).
Your explained scenario is possible only if customer have already uploaded a "hello.txt" object before versioning suspension. Once versioning is suspended, all subsequent DELETE operations will produce a delete marker but the original object is really deleted(Customer should have seen only a Delete Marker and not the original object after deletion[Step 7]).
As per the documentation, once versioning is enabled and then suspended, bucket behavior can never be reverted to 'disabled versioning' state.
answered 3 years ago
Relevant questions
S3 Bucket Delete Marker Policy Not Working
asked 5 months agoAWS Transfer Family cannot download with S3 Versioning enabled
asked 2 years agoHow can customers find out the S3 bucket with the highest cost or sort the cost for each S3 bucket?
Accepted Answerasked 2 years agoWhy do we need S3 bucket versioning enabled in order to do replication?
Accepted Answerasked a year agoS3 Bucket Object Versioning & Lifecycle Rules - Applied to Existing Objects or only New?
Accepted Answerasked 5 years agoDoes S3 charge for delete marker objects with a Null ID?
Accepted Answerasked 3 years agoFile deletion with datasync if versioning is enabled.
Accepted Answerasked 3 years agoS3 Event Bridge events have null values for VersionId. Is this a bug?
asked 8 months agoCustomising the Customer Profile
asked 2 months agoS3 Inventory : Is there a limit to the number of objects in a bucket that will show up in the inventory?
Accepted Answerasked 4 years ago