1 個回答
- 最新
- 最多得票
- 最多評論
1
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.
已回答 5 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前