Object Lock and Retention
What you'll learn: How to make cloud objects permanently unchangeable for compliance and regulatory needs.
What Is Object Lock?
Object Lock enforces write-once-read-many (WORM) protection on your stored objects. Once locked, objects cannot be overwritten or deleted for a specified period—or ever. Think of it like sealing a document in a time-locked vault: once inside, nobody (not even you) can alter or remove it until the timer expires.
This feature is critical for industries with strict regulatory requirements—finance, healthcare, legal—where data integrity and tamper-proof records are mandatory.
Two Lock Modes
Governance Mode provides flexible protection. Users with special permissions can still remove locks or delete objects if absolutely necessary. It's like a manager having override keys to the vault.
Compliance Mode is iron-clad. Nobody—not even the account owner or cloud provider—can delete or modify the object until retention expires. This satisfies the strictest legal requirements where immutability must be guaranteed.
How Retention Works
When you apply Object Lock, you set a retention period (e.g., 7 years). The object remains untouchable until that date passes. You can also enable legal holds—indefinite locks that stay active until explicitly removed, useful during ongoing investigations.
Object Lock integrates with versioning (from lesson 156): each version can have its own retention settings, ensuring complete audit trails.
Real-World Example
A hospital stores patient records with a 10-year compliance-mode retention. Even if someone tries to delete records to hide mistakes, the system refuses. Auditors can trust the data hasn't been tampered with.
Key Takeaway: Object Lock enforces immutability with governance (flexible) or compliance (strict) modes, guaranteeing regulatory-compliant, tamper-proof storage for sensitive data.