Suspended Versioning

Scenario:

Step 1: You have bucket versioning enabled initially.

**Step 2: **You suspend versioning and upload an object (let's call it file.txt). This object will have a null version ID.

Step 3: You then re-enable versioning and upload file.txt again with the same name.

Outcome:

Versioning Suspended: When you upload file.txt while versioning is suspended, S3 treats it as an unversioned object and assigns it a null version ID.

Versioning Enabled Again: When you re-enable versioning and upload file.txt again, S3 will create a new version of the object with a unique version ID.

Result:

Two Versions of the Object:

There will be two versions of file.txt:

null version ID: The object uploaded when versioning was suspended.

A new version ID: The object uploaded after re-enabling versioning.

The null version remains associated with the object from when versioning was suspended, and any new uploads after versioning is re-enabled will receive unique version IDs.

This means that S3 does not overwrite the null version but instead creates a new version with a different version ID.

please refer once below document

https://docs.aws.amazon.com/AmazonS3/latest/userguide/AddingObjectstoVersionSuspendedBuckets.html#:~:text=If%20a%20null%20version%20is%20already%20in%20the,PUT%20becomes%20the%20current%20version%20of%20the%20object.