compliance mode
An S3 Object Lock setting where nobody, not even the account's root user, can delete a locked object or shorten its retention before it expires.
In more detail
Compliance mode gives the strongest protection for backups because no stolen credential can undo it. The same rule cuts both ways: if you set the retention too long or lock the wrong data, you have to wait for it to expire or close the account. Test the settings in governance mode first, then switch to compliance mode for the copy that must survive an attacker.
Example
"DefaultRetention": {"Days": 30, "Mode": "COMPLIANCE"}Related terms
- governance mode — An S3 Object Lock setting where locked objects are protected from most users, but people with a special permission can still delete them early.
- S3 Object Lock — An S3 feature that stores objects in write-once, read-many form, so they cannot be deleted or overwritten until a retention date.
- immutable — Something that cannot be changed after it is created; to change it you make a new one.
- root user — The all-powerful administrator account on Linux, with user ID 0, which can read or change anything.
Taught in
- Private Paths: VPC Endpoints And PrivateLink — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Protecting Data: Versions, Object Lock, Backups And Secrets — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Long-Stem Clinic: The Phrase That Decides — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography