Choose the action that preserves the correct object version and proves it can be read. Separate retained bytes, current-key visibility, notification delivery, and application acceptance.
Review these lessons
- Object version recovery: distinguish a delete marker from lost bytes
- Object lifecycle rules: model current, noncurrent, and archive states
- Multipart uploads: bound abandoned parts and retry cost
- Object integrity: verify bytes without trusting an ETag shortcut
- Object events: survive duplicate delivery and stale notifications
- Presigned object access: bound authority and expiry
- Locked objects: test retention, legal hold, and decryption together
- Object inventory: reconcile delayed snapshots with live decisions
Other checks
Common Mistakes
- Do not infer permanent loss from a current-key miss.
- Do not treat an inventory snapshot as live state.
