S3 versioning in AWS - Step-by-Step Execution

Process Flow - S3 versioning

Create S3 Bucket

↓

Enable Versioning

↓

Upload Object v1

↓

Upload Object v2 (same key)

↓

Store multiple versions

↓

Retrieve or Delete specific version

This flow shows creating a bucket, enabling versioning, uploading objects with the same name to create versions, and managing those versions.

Execution Sample

AWS

aws s3api create-bucket --bucket my-bucket --region us-east-1
aws s3api put-bucket-versioning --bucket my-bucket --versioning-configuration Status=Enabled
aws s3api put-object --bucket my-bucket --key file.txt --body file_v1.txt
aws s3api put-object --bucket my-bucket --key file.txt --body file_v2.txt

This code creates a bucket, enables versioning, then uploads two versions of the same file.

Process Table

Step	Action	Bucket Versioning Status	Object Key	Version ID Created	Notes
1	Create bucket 'my-bucket'	Disabled (default)	-	-	Bucket created without versioning
2	Enable versioning on 'my-bucket'	Enabled	-	-	Versioning turned on
3	Upload 'file.txt' with content v1	Enabled	file.txt	v1-id-123	First version stored
4	Upload 'file.txt' with content v2	Enabled	file.txt	v2-id-456	Second version stored, old version kept
5	Retrieve 'file.txt' without version ID	Enabled	file.txt	v2-id-456	Latest version returned
6	Retrieve 'file.txt' with version ID 'v1-id-123'	Enabled	file.txt	v1-id-123	First version returned
7	Delete 'file.txt' without version ID	Enabled	file.txt	Delete Marker ID	Delete marker added, object hidden but versions kept
8	Delete 'file.txt' with version ID 'v1-id-123'	Enabled	file.txt	v1-id-123	Specific version deleted, others remain

💡 Versioning keeps all versions; delete without version ID adds delete marker; delete with version ID removes that version only.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 7	Final
Bucket Versioning Status	Disabled	Enabled	Enabled	Enabled	Enabled	Enabled
file.txt Versions	None	None	v1-id-123	v1-id-123, v2-id-456	v1-id-123, v2-id-456 + Delete Marker	v2-id-456 + Delete Marker
Latest Version ID	None	None	v1-id-123	v2-id-456	Delete Marker	Delete Marker

Key Moments - 3 Insights

Why does deleting an object without a version ID not remove all versions?

Because with versioning enabled, deleting without specifying a version adds a delete marker (see step 7), hiding the object but keeping all versions intact.

How can you retrieve an older version of an object?

By specifying the version ID when retrieving the object (see step 6), you get that exact version instead of the latest.

What happens if you upload a file with the same key after enabling versioning?

A new version is created and stored alongside previous versions (see step 4), so no data is lost.

Visual Quiz - 3 Questions

Look at the execution table, what is the bucket versioning status after step 3?

A Enabled

B Disabled

C Suspended

D Not set

💡 Hint

Check the 'Bucket Versioning Status' column at step 3 in the execution table.

At which step is the delete marker added to the object versions?

A Step 4

B Step 8

C Step 7

D Step 6

💡 Hint

Look for the note mentioning 'Delete Marker' in the execution table.

If versioning was not enabled, what would happen when uploading the second 'file.txt'?

A Both versions would be stored separately

B The second upload would overwrite the first without keeping versions

C An error would occur

D A delete marker would be added

💡 Hint

Refer to the concept flow and the importance of enabling versioning before uploading multiple versions.

Concept Snapshot

S3 Versioning:
- Enable versioning on a bucket to keep multiple versions of objects.
- Uploading an object with the same key creates a new version.
- Deleting without version ID adds a delete marker, hiding the object.
- Retrieve or delete specific versions by specifying version IDs.
- Versioning protects data from accidental overwrites or deletions.

Full Transcript

This visual execution shows how S3 versioning works step-by-step. First, a bucket is created without versioning. Then versioning is enabled. Uploading a file creates a version. Uploading again with the same name creates a new version, keeping the old one. Retrieving without version ID gets the latest version. Retrieving with version ID gets that specific version. Deleting without version ID adds a delete marker, hiding the object but keeping versions. Deleting with version ID removes that version only. This protects data from accidental loss.

Practice

1. What is the main purpose of enabling S3 versioning on a bucket?

easy

A. To keep multiple copies of files automatically for recovery and tracking

B. To increase the storage capacity of the bucket

C. To encrypt files stored in the bucket

D. To restrict access to the bucket

Solution

1. Step 1: Understand what S3 versioning does

   S3 versioning keeps multiple versions of the same file automatically.

2. Step 2: Identify the main benefit

   This helps recover from mistakes and track changes over time.

3. Final Answer:

   To keep multiple copies of files automatically for recovery and tracking -> Option A

4. Quick Check:

   S3 versioning = multiple copies for recovery [OK]

Hint: Versioning means saving file copies automatically [OK]

Common Mistakes:

• Thinking versioning increases storage size limit
• Confusing versioning with encryption
• Assuming versioning controls access permissions

2. Which of the following is the correct way to enable versioning in an AWS S3 bucket configuration?

easy

A. versioning = true

B. versioning { enabled = true }

C. enable_versioning = yes

D. versioning: active

Solution

1. Step 1: Recall the syntax for enabling versioning

   Versioning is enabled by setting a block with enabled = true.

2. Step 2: Match the correct syntax

   Only versioning { enabled = true } matches the correct structure.

3. Final Answer:

   versioning { enabled = true } -> Option B

4. Quick Check:

   Enable versioning with block and enabled=true [OK]

Hint: Look for block with enabled = true syntax [OK]

Common Mistakes:

• Using assignment without block braces
• Using yes/no instead of true/false
• Using colon instead of equals sign

3. Given the following Terraform snippet for an S3 bucket, what will be the versioning state of the bucket after deployment?

resource "aws_s3_bucket" "example" {
  bucket = "my-versioned-bucket"

  versioning {
    enabled = false
  }
}

medium

A. Versioning will be enabled and keep all versions

B. Versioning will be enabled but only for new files

C. Versioning will be suspended, no new versions saved

D. Versioning will be enabled with MFA delete

Solution

1. Step 1: Check the versioning block value

   The snippet sets enabled = false, which means versioning is suspended.

2. Step 2: Understand suspended versioning behavior

   Suspended versioning means no new versions are saved, but existing versions remain.

3. Final Answer:

   Versioning will be suspended, no new versions saved -> Option C

4. Quick Check:

   enabled = false means versioning suspended [OK]

Hint: enabled = false means versioning suspended, not enabled [OK]

Common Mistakes:

• Assuming false means versioning enabled
• Confusing suspended with disabled (deleted)
• Thinking MFA delete is enabled by default

4. You wrote this Terraform code to enable versioning but it does not work as expected:

resource "aws_s3_bucket" "mybucket" {
  bucket = "mybucket"
  versioning = {
    enabled = true
  }
}

What is the error and how to fix it?

medium

A. enabled must be a string "true", not boolean true

B. Versioning cannot be enabled during bucket creation

C. Bucket name must be unique globally

D. versioning should be a block, not an assignment; remove '='

Solution

1. Step 1: Identify syntax error in versioning block

   The code uses versioning = { ... } which is incorrect syntax for a block.

2. Step 2: Correct syntax for versioning block

   Versioning must be declared as a block without '=' like versioning { enabled = true }.

3. Final Answer:

   versioning should be a block, not an assignment; remove '=' -> Option D

4. Quick Check:

   Blocks use braces without '=' [OK]

Hint: Blocks use braces without '=' sign [OK]

Common Mistakes:

• Using '=' with blocks
• Using string instead of boolean for enabled
• Ignoring bucket name uniqueness errors

5. You want to protect important files in your S3 bucket from accidental deletion but still allow updates. How does enabling versioning help achieve this, and what additional step should you take for stronger protection?

hard

A. Versioning keeps old file copies; enable MFA delete to require extra confirmation for deletions

B. Versioning encrypts files; enable bucket policies to restrict access

C. Versioning compresses files; enable lifecycle rules to archive old versions

D. Versioning increases storage; enable logging to track deletions

Solution

1. Step 1: Understand versioning's role in protection

   Versioning keeps all versions of files, so deleted files can be recovered.

2. Step 2: Identify additional protection for deletions

   Enabling MFA delete adds a requirement for multi-factor authentication to delete versions, preventing accidental or unauthorized deletions.

3. Final Answer:

   Versioning keeps old file copies; enable MFA delete to require extra confirmation for deletions -> Option A

4. Quick Check:

   Versioning + MFA delete = strong deletion protection [OK]

Hint: Use MFA delete with versioning for deletion safety [OK]

Common Mistakes:

• Confusing encryption with versioning
• Thinking lifecycle rules prevent deletions
• Assuming logging stops accidental deletes