Before production use, a general-purpose S3 bucket will store important files. Recover within seven days from future overwrites or accidental deletes that omit versionId, using retained earlier versions.
Do not expire noncurrent versions within seven days, and prepare restore permissions. Protection against permanent deletion of every version is a separate concern.
Which basic configuration is most appropriate?
Enable S3 Versioning in advance and restore using retained versions and delete markers; manage retention and permanent-deletion access separately.
Detailed explanation
Versioning does not recreate content already lost before enablement; preservation must happen first.
Versioning does not recreate content already lost before enablement; preservation must happen first.
Suspension differs from enabled version accumulation; repeated overwrites of the null version can lose history.
Suspension differs from enabled version accumulation; repeated overwrites of the null version can lose history.
Future overwrites retain distinct versions; a delete without versionId creates a delete marker. Retained versions can support restoration.
Future overwrites retain distinct versions; a delete without versionId creates a delete marker. Retained versions can support restoration.
Permanent expiration can remove the recovery source. One-day retention conflicts with this requirement.
Permanent expiration can remove the recovery source. One-day retention conflicts with this requirement.
Check official documentation
Compare the following points with the official documentation.
Review enabled/suspended behavior, version-specific deletion and markers, and restoration of previous versions.
Official references
- Official documentation 1
- Official documentation 2
- Official documentation 3
- Official documentation 4
- Official documentation 5
- Official documentation 6
What to confirm
Explain prior-version copying for overwrites, marker handling for simple deletes, and why permanently deleted versions cannot be recovered.
Key points
- S3 Versioning
- Delete marker
- versionId
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-04.
Foundation review
Distinguish overwrite and simple-delete recovery
In an enabled general-purpose bucket, overwriting creates a new version and deleting without versionId creates a marker. Copy the desired retained version to the same key to make a new current version after an overwrite. For a simple delete, inspect the current marker and remaining versions; removing the appropriate marker by its versionId can restore access.
Recovery requires retained history
Enabling Versioning later cannot revive already lost content. Check suspended null-version behavior, noncurrent lifecycle expiration, and permanent version-specific deletion separately. Without a retained version, Versioning alone cannot restore content. Each version stores the entire object, so review retention and storage cost operationally.