Cloud concept · Updated

Immutable Backups - Immutable backups are recovery copies protected against modification and premature deletion for an enforced retention period.

In short

Backup immutability preserves recovery points even when production systems or administrative credentials are compromised. It helps defend against ransomware and accidental deletion, but must be combined with isolated administration, protected encryption keys, and tested recovery procedures.

Cloud Concepts Hub →

6 key aspects of Immutable Backups

Effective immutable backups combine enforced retention, constrained administration, protected encryption keys, and validated recovery over an appropriate retention window.

01
Storage-enforced retention

Protect recovery points against modification and deletion until their retention expires. A backup schedule or an IAM policy alone does not provide equivalent protection against administrators who can change those settings.

02
Explicit administrative bypass rules

Choose protection based on whether privileged users must retain a bypass capability. Compliance-style locks provide stronger resistance to credential compromise but can become irreversible after an applicable grace period.

03
Isolated recovery copies

Separate backup administration from production administration, commonly through a dedicated account and restricted roles. Use cross-Region copies where regional failure is part of the threat model, while verifying resource and encryption support.

04
Recoverable encryption

Protect encryption keys for at least as long as the backups require them. Restrict key disablement and deletion because immutable ciphertext is not useful if its key is unavailable.

05
Known-good recovery validation

Regularly restore protected recovery points and validate application consistency. Keep enough history to recover from corruption or compromise discovered well after the initial event.

06
Deliberate retention economics

Balance recovery history against storage costs, retrieval delays, and deletion obligations. Validate retention settings before applying an irreversible lock.

Cloud services for Immutable Backups

AWS Backup can schedule recovery points and copy supported backups into separately administered vaults, where Vault Lock enforces retention. S3 Object Lock protects object versions used as backup data, while EBS Snapshot Lock protects individual EBS snapshots. Amazon Data Lifecycle Manager handles supported snapshot and image lifecycle automation, and AWS DataSync moves data into supported storage destinations; neither should be mistaken for an immutability control. Coordinate scheduling, copying, and lifecycle expiration with destination locks so automated deletion cannot undermine retention requirements. Across these services, isolate administrative permissions, protect encryption keys, monitor failures, and test restoration of known-good data.

AWS BackupAWS Backup

AWS Backup coordinates backup policies and supported backup copies, while AWS Backup Vault Lock enforces retention protections within a vault. Governance mode allows authorized removal of the lock; compliance mode makes the lock immutable after its grace period.

Amazon S3Amazon S3

S3 Object Lock provides write-once, read-many protection for object versions through retention periods and legal holds. Compliance retention prevents deletion or shortening of retention even by the account root user, while governance retention permits explicitly authorized bypass.

AWS DataSyncAWS DataSync

AWS DataSync transfers data between supported storage systems, including S3 destinations used for backup copies. It does not itself enforce immutability; configure destination protection separately and verify how transfer settings interact with object versions and retention.

Immutable Backups exam questions

Real practice exam questions on Immutable Backups, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAP-C03

A healthcare software company stores application recovery packages in an existing Amazon S3 general purpose bucket that has never had S3 Versioning enabled. The application replaces each package by issuing a PUT request to the same object key. Changing the bucket name, object keys, or upload behavior would require a lengthy application release.

Beginning at a planned cutover, every successfully uploaded package must remain recoverable for at least 60 days after its upload, even if ransomware subsequently uploads corrupted content to the same key. No identity, including the AWS account root user, may permanently delete a protected package or shorten its established retention. Operators must be able to make a retained package the current package again without changing the key used by readers. Packages that exist before cutover do not require retention protection.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Enable S3 Versioning and S3 Object Lock on the existing bucket before cutover. Configure default 60-day compliance-mode retention, and ensure uploads cannot specify shorter retention. Keep versioning enabled. Recover a package by copying its retained version to the same key, creating a new current version.

Object Lock can be enabled on an existing general purpose bucket and requires Versioning. Compliance-mode retention prevents permanent deletion or shortening of an established retention period, including by the root user. Protection applies to individual versions: a PUT to the same key creates another version without modifying the retained version. Copying a retained version back to the same key creates a new current version. After Object Lock is enabled, it cannot be disabled and versioning cannot be suspended.

SCS-C03

A company runs applications on Amazon EC2 instances with encrypted Amazon EBS volumes. Amazon Data Lifecycle Manager creates daily EBS snapshots and retains them for 90 days. A security review finds that a compromised production administrator could delete the snapshots before their retention periods end. The encryption keys are administered separately and cannot be disabled or deleted by production administrators.

The company must protect existing and future snapshots in place, without creating additional backup copies. After any configured cooling-off period expires, even an administrator with full EC2 permissions must be unable to delete a protected snapshot before its 90-day retention expiration date. Which solution meets these requirements?

Show answerCORRECT ANSWER

Apply EBS Snapshot Lock in compliance mode to the existing snapshots, and automate its application to future snapshots. Set each lock expiration to the required retention expiration date and allow the cooling-off period to expire.

EBS Snapshot Lock in compliance mode prevents snapshot deletion until the lock expires. After the cooling-off period ends, privileged administrators cannot remove or shorten the protection. It applies directly to existing EBS snapshots without requiring additional backup copies. Future snapshots must also have the lock applied.

Practice Immutable Backups in a full exam

Questions on Immutable Backups in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Immutable Backups

3 min read

Immutable backups preserve a recovery copy in a state that cannot be overwritten or deleted before its protection period ends. The essential control is storage-enforced retention, rather than a convention that administrators should not delete backups. This distinction matters during ransomware incidents: an attacker with production administrator credentials may attempt to destroy recovery points before encrypting live data.

Cloud implementations commonly use write-once, read-many storage, locked backup vaults, or snapshot retention locks. A backup policy determines when recovery points are created and how long they should be retained; an immutability control prevents prohibited changes to those recovery points. Scheduling backups alone does not provide immutability, and ordinary access policies may be insufficient when an attacker can change those policies.

Protection modes have different trust boundaries. Governance-style controls permit designated privileged identities to bypass or remove protection, making them useful where operational flexibility is required. Compliance-style controls prevent even highly privileged administrators from shortening established protection after any applicable configuration or cooling-off period. Engineers must understand when a lock becomes irreversible and which recovery points it protects before enabling it in production.

For example, an organization could create daily recovery points, copy supported backups into a dedicated backup account, and enforce retention in the destination vault. Production administrators should not control destination retention settings, backup deletion, or encryption-key administration. Cross-Region copies can additionally address regional disruption. Cross-account and cross-Region copying depend on resource support and encryption requirements, so the design must be checked for each workload rather than assumed to work uniformly.

On AWS, AWS Backup Vault Lock can enforce retention for recovery points in a backup vault. Amazon S3 Object Lock protects individual object versions using retention periods or legal holds, and requires S3 Versioning. New object versions can still be created, so protecting an older version does not prevent an attacker from uploading a corrupted replacement as the current version. Recovery procedures must identify and retrieve the known-good protected version. Amazon EBS Snapshot Lock provides retention protection for EBS snapshots independently of the mechanism that schedules their creation.

Replication and transfer are not substitutes for immutability. Replication can copy corrupted or encrypted source data into the destination, while synchronization may propagate unwanted changes according to its configuration. AWS DataSync moves data but does not inherently make the destination immutable. Similarly, Amazon Data Lifecycle Manager automates supported snapshot and image lifecycle operations but should not be treated as a retention lock. Transfer, replication, lifecycle management, and destination protection must be designed as separate controls.

Immutability also does not guarantee recoverability. A protected backup can contain malware, incomplete application state, or already-corrupted data. An attacker who cannot delete encrypted backups might still render them unusable by disabling or deleting their encryption keys. Protect key administration separately, retain necessary keys, monitor backup failures and retention changes, and regularly restore representative workloads into an isolated environment. Measure recovery point objectives and recovery time objectives rather than assuming a successful backup job proves that recovery will meet business requirements.

The principal trade-offs are storage cost, reduced deletion flexibility, and operational complexity. Long retention preserves more recovery options but increases costs and can conflict with data-deletion obligations. Irreversible locks can retain mistakenly captured sensitive data or unexpectedly large backups until protection expires. Test policies with nonproduction data, align retention with legal requirements and ransomware detection windows, and account for restore charges, archive retrieval delays, and application dependencies.

Learn Immutable Backups in lessons

5 short lessons on Immutable Backups in 2 certification courses.

Open the lessons