Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is S3 Object Lock and Immutable Backup?

S3 Object Lock applies write-once-read-many retention to stored objects, so a backup cannot be deleted or overwritten — by an attacker, by automation, or by an administrator — until its retention expires.

Illustration for the cybersecurity term S3 Object Lock
Home / Blog / Cybersecurity Terms / What Is S3 Object Lock and Immutable Backup?
17 November 2026

What Is S3 Object Lock and Immutable Backup?

What Is S3 Object Lock and Immutable Backup?

S3 Object Lock is an Amazon S3 feature that applies write-once-read-many retention to object versions. While a lock is in force, that version cannot be overwritten or deleted — not by the application that wrote it, not by automation, and depending on the mode, not by the account root user either. Immutable backup is the practice built on top of it: keeping at least one copy of your data that nobody with live credentials can destroy.

Why Immutability Became Necessary

Ransomware groups learned years ago that encrypting production is only half the job. Current playbooks begin by finding and destroying recovery capability: deleting snapshots, wiping backup catalogues, revoking the backup service account, and targeting backup software directly. Published advisories on LockBit and Conti affiliate activity describe exactly this sequence, and in cloud estates it is faster than on-premises because a single set of credentials can reach every copy through an API.

Immutability changes the arithmetic. If the most recent clean copy cannot be deleted for thirty days regardless of who asks, the attacker’s leverage disappears even if they hold administrative access. That is a materially different position from “we have backups”, which was also true of most organisations that ended up paying.

How Object Lock Works

Object Lock requires versioning to be enabled on the bucket, and it protects object versions rather than object names. A new upload creates a new version; the locked one remains retrievable.

ModeWho can shorten or remove itTypical use
GovernanceA principal holding s3:BypassGovernanceRetentionOperational protection with a documented override
ComplianceNobody, including the account root user, until the date passesRegulatory retention and ransomware resilience
Legal holdAny principal with s3:PutObjectLegalHoldIndefinite preservation for litigation or an investigation

Retention is set either per object with a retain-until date or through a bucket default that applies a fixed period to every new upload. Legal holds work independently of retention periods and have no expiry, which makes them the right tool when you need to freeze evidence during an incident response and do not yet know for how long.

Compliance mode deserves a warning that is easy to skip over. It is genuinely irreversible. An error in a bucket default — a retention of ten years applied to a chatty log stream, for example — cannot be corrected and will be billed for the full period. Test the configuration in a scratch bucket with a retention measured in days before applying it anywhere that matters.

The Equivalents on Other Platforms

Azure Blob Storage offers immutable storage with time-based retention policies and legal holds, applied at container or version level, with a locked policy behaving much like compliance mode. Google Cloud Storage provides bucket retention policies that can themselves be locked, after which the policy cannot be shortened or removed. Most enterprise backup products — Veeam, Commvault, Rubrik and others — can write to all three and will set the retention flag for you, which is usually a better path than scripting it yourself.

Making It a Real Control

Immutability is undermined by the architecture around it more often than by the feature itself.

Regulation and Assurance

Financial services firms have long used write-once storage to satisfy record-keeping rules, and cloud providers publish third-party assessments confirming that compliance mode meets those requirements. The newer driver is resilience: DORA requires financial entities in the EU to maintain and test recovery capability, the UK operational resilience framework expects firms to remain within impact tolerances for important business services, and NCSC ransomware guidance is explicit that backups must be out of reach of an attacker who has compromised the network. An immutable copy is the clearest way to evidence all three.

Immutable storage works best as one layer of a multi-region backup strategy. If you want to know whether your recovery would survive a determined attacker, our emergency action plan services start from that assumption.

FAQ – Frequently Asked Questions

Can I Enable Object Lock on a Bucket I Already Have?

Versioning must be enabled first, and historically Object Lock could only be set when the bucket was created. AWS now supports enabling it on existing versioned buckets through the API, though the safer route for an established estate is usually to create a purpose-built bucket in a separate account and replicate into it. That also gives you the account separation immutability depends on.

What Is the Difference Between Governance and Compliance Mode?

Governance mode can be overridden by a principal holding the bypass permission, which makes it suitable when you want protection against mistakes and routine attacks while retaining an emergency escape. Compliance mode cannot be overridden by anyone, including the root user, until the retention date passes. Choose compliance mode for regulatory retention and for the copy that must survive a full administrative compromise.

Does Object Lock Stop Ransomware Completely?

It stops an attacker destroying the locked copies, which is what turns an incident into an extinction event. It does not prevent the initial compromise, data theft and extortion, or encryption of production systems, and it does not help if the retention period is shorter than the time you take to detect the intrusion. Treat it as recovery assurance rather than prevention.

How Much Does Immutable Storage Cost?

Object Lock itself carries no additional charge; you pay for the storage that retention forces you to keep. Because locked versions cannot be removed early, lifecycle rules cannot trim them, so costs are driven by retention length and how often objects change. Model it before committing: a short retention on frequently rewritten data can cost far more than a long retention on stable archives.

Related Terms

You May Be Interested In These

What Is gRPC Security?

Cybersecurity Terms

17 November 2026

What Is gRPC Security?

Read More
What Are DANE and TLSA?

Cybersecurity Terms

17 November 2026

What Are DANE and TLSA?

Read More
What Is an SMB Relay Attack?

Cybersecurity Terms

17 November 2026

What Is an SMB Relay Attack?

Read More