Security
S3 Object Lock explained: retention needs to be designed before upload
Object Lock can protect object versions from deletion for a retention period when the backend supports it. It is powerful because the restriction is enforced at the storage layer, and that same power means the consequences must be understood before enabling it.
Object Lock normally works with versioned objects
Retention applies to specific object versions. It does not freeze an entire application. The bucket configuration and provider implementation determine which lock modes and operations are available.
Verify versioning and lock status through the storage API or provider backend. A client checkbox is not enough evidence. An upload to an unlocked bucket cannot be made immutable by calling the marketing page immutable.
Some providers require lock at bucket creation
If Object Lock must be enabled when a bucket is created, it is an architectural decision, not a toggle to add after a customer has filled the bucket. The provisioning workflow needs a separate locked-service option or explicit default.
Document this before public checkout so customers do not learn the limitation after storing terabytes of data.
Retention can block legitimate deletion
Locked versions consume storage until their retention conditions allow removal. A mistaken policy can prevent a customer from reducing capacity or purging sensitive data on the expected schedule.
Capacity planning needs to include retained versions, and termination procedures must define what happens when provider-enforced retention outlives the WHMCS service.
Credentials still matter
Object Lock does not make leaked read credentials harmless. Scope data access, protect secrets and separate administrative retention privileges from ordinary backup writers.
Test the exact deletion actions a compromised backup account could perform. Security claims should be based on failed negative tests, not on the presence of a lock setting.
Use a written retention policy
Define how long data must remain, who may change retention, how legal or business deletion requirements are handled and how capacity is funded during the lock period.
A technical retention feature should implement a written policy with known owners and durations.