Ravi Sir's Cards › AWS
Object Lock and WORM
This revision card explains Object Lock and WORM. It starts from the need that evidence and invoices must not vanish after a bad script. It describes enable Object Lock at create; COMPLIANCE/GOVERNANCE retention; Deny DeleteObject in policy; MFA Delete on versioning. The how-to section covers how to create with lock , then put object with retain , then delete fails , then document legal hold. An example on the card is priya Nair compliance bucket uses COMPLIANCE 30-day lab retention.
Read card text
What this card says
Why do we need it?
Evidence and invoices must not vanish after a bad script.
What is it?
Enable Object Lock at create; COMPLIANCE/GOVERNANCE retention; Deny DeleteObject in policy; MFA Delete on versioning.
Object Lock
How to do it
Create with lock → put object with retain → delete fails → document legal hold.
Example
Priya Nair compliance bucket uses COMPLIANCE 30-day lab retention.