Cloud concept · Updated

Legal Holds - Legal holds are preservation controls that suspend routine deletion or alteration of relevant information until an authorized release.

In short

A legal hold preserves information needed for litigation, investigations, or other legal obligations, usually without a predetermined expiration date. In cloud environments, engineers translate that obligation into enforceable storage and backup controls, supported by access restrictions, audit records, and reliable retrieval procedures.

Cloud Concepts Hub →

6 key aspects of Legal Holds

Effective legal holds combine precise scope, enforceable preservation, independent retention controls, authorized release, and continued access to usable evidence.

01
Preservation until authorized release

A legal hold generally remains active without a fixed expiration date. Require documented authorization before releasing protection rather than relying on ordinary lifecycle schedules.

02
Precisely defined scope

Identify the object versions, recovery points, records, and time ranges that must be preserved. Include relevant historical data and newly created information when the preservation obligation requires it.

03
Independence from retention periods

Legal holds and time-based retention can protect the same data simultaneously. Permanent deletion must remain blocked until the hold is released and any remaining retention requirements are satisfied.

04
Lifecycle-aware deletion protection

Use enforceable storage or backup controls rather than labels alone. Storage-class transitions may remain permissible, but automatic expiration must not delete protected evidence.

05
Controlled and auditable administration

Restrict permissions to apply and remove holds, separating them from routine application access. Record administrative actions and review release requests against the applicable legal authorization.

06
Continued evidence usability

Preserve encryption keys, identifiers, metadata, and retrieval procedures alongside the data. Test recovery and account for archive retrieval delays, backup coverage, and ongoing costs.

Cloud services for Legal Holds

Amazon S3 and AWS Backup enforce preservation for different data representations: object versions and supported backup recovery points. CloudTrail supplies audit records for relevant administrative and access activity, while AWS KMS supports the continued readability of encrypted evidence. Coordinate these services through a workflow that identifies scope, applies protection, verifies coverage, tests retrieval, and authorizes release. Lifecycle rules can optimize storage where compatible with preservation, but they must not determine when a legal hold ends. Protect audit records, metadata, and encryption dependencies as well as the primary evidence.

Amazon S3Amazon S3

S3 Object Lock implements legal holds on individual object versions independently of time-based retention. S3 Lifecycle can transition protected versions between storage classes but cannot permanently delete versions while Object Lock protection applies.

AWS BackupAWS Backup

AWS Backup legal holds preserve selected supported recovery points against deletion even when their scheduled retention expires. Verify resource and recovery-point eligibility, and distinguish legal holds from the retention constraints enforced by AWS Backup Vault Lock.

AWS CloudTrailAWS CloudTrail

CloudTrail records supported hold-management and data-access API activity for auditing. Configure the appropriate event categories, including S3 object-level data events where required, and protect the resulting audit records.

Legal Holds exam questions

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

DEA-C01

A company stores investigation exports in an Amazon S3 bucket with versioning and S3 Object Lock enabled. Each export version has a compliance-mode retention period and was also placed under a legal hold. The legal team has now authorized release of the holds and requested permanent deletion at the earliest time permitted by the remaining storage protections.

A data engineer sets the legal-hold status to OFF for every version in the approved deletion manifest. All listed versions still have compliance-mode retention dates 60 days in the future. No other preservation requirements apply.

How should the engineer complete the deletion workflow?

Show answerCORRECT ANSWER

Keep the listed versions until their compliance retention dates expire, and then permanently delete them by specifying their version IDs.

Legal holds and time-based retention are independent protections. Turning a legal hold OFF does not cancel unexpired compliance-mode retention. Once that retention expires, the workflow can permanently delete the approved versions using their version IDs.

SCS-C03

A company uses AWS Backup to create daily recovery points for its production file systems. Each recovery point has a 35-day retention period. During an investigation, the legal team requires all existing recovery points for three specified file systems created within a particular 10-day period to be preserved until the legal team explicitly authorizes their release. The investigation has no known end date. Other recovery points must continue to expire normally. The company must not create additional backup copies or change the selected recovery points' configured lifecycle settings.

Which solution meets these requirements with the least operational overhead?

Show answerCORRECT ANSWER

Create an AWS Backup legal hold that selects the three file systems by resource ARN and specifies the required recovery point creation date range. Leave the backup plan and recovery point lifecycles unchanged, and release the hold only after legal authorization.

An AWS Backup legal hold preserves matching recovery points until the hold is explicitly released, even if their configured retention periods expire. Resource ARNs and a creation date range scope preservation to the required recovery points without changing their lifecycle settings or preventing unrelated recovery points from expiring.

SAA-C03

A company stores investigation evidence in an Amazon S3 Standard bucket with versioning and S3 Object Lock enabled. The evidence team applied a legal hold to a particular object version and recorded its version ID.

An application subsequently issued a successful DeleteObject request for the same object key without specifying a version ID. Requests to download the object by using only its key now return HTTP 404. The evidence team confirms that the recorded version still has its legal-hold status set to ON.

A solutions architect must retrieve the preserved evidence without changing any object versions or removing their protection. Which action should the solutions architect take?

Show answerCORRECT ANSWER

Issue a GetObject request that includes the evidence object's recorded version ID.

A DeleteObject request without a version ID can create a delete marker even when an underlying version has a legal hold. The hold prevents permanent deletion of the protected version, not creation of a delete marker. Specifying the preserved version ID retrieves the evidence without changing its protection or the object's current view.

Practice Legal Holds in a full exam

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

Start a free practice exam

What is Legal Holds

3 min read

A legal hold prevents the routine disposal of information that must remain available for a legal matter or investigation. Unlike a retention policy that preserves records for a defined period, a legal hold generally continues until explicitly released. Legal or records-management teams determine the preservation obligation, while engineers implement controls that protect the relevant data and demonstrate that those controls remain effective.

Start by defining the scope of preservation. Relevant information might include customer transactions, application logs, previous object versions, file-system data, or database recovery points. Record identifiers, timestamps, ownership, case references, and the systems containing additional copies. A tag or case label can help locate evidence, but it does not itself prevent deletion. A one-time snapshot also does not automatically preserve relevant information created after that snapshot.

Cloud object storage can enforce preservation on individual object versions. For example, Amazon S3 Object Lock supports legal holds on object versions in an Object Lock-enabled bucket. A legal hold has an ON or OFF state and no automatic expiration date. While the hold is active, the protected version cannot be permanently deleted. Applications can still create newer versions, and a delete marker can hide the object from ordinary reads. Preservation therefore protects the underlying evidence without necessarily freezing the application's current view.

Legal holds and time-based retention are independent controls. In S3, a legal hold can coexist with governance-mode or compliance-mode retention. Expiration of a retention period does not release an active legal hold, and removing a hold does not cancel an unexpired retention requirement. Permission to bypass governance retention does not bypass a legal hold. However, a principal authorized to change the legal-hold state can remove it, making restricted administration and monitored release procedures essential.

Automatic lifecycle management must distinguish storage optimization from disposal. S3 Lifecycle can transition protected versions between storage classes, but it cannot permanently delete a version while Object Lock protection applies. Archiving can reduce storage costs while adding retrieval delays and charges. After a hold is released, data that already meets lifecycle expiration conditions can become eligible for deletion if no other protection remains. Release workflows should therefore evaluate disposal consequences before changing protection.

Backup preservation applies the same principle to recovery points. AWS Backup legal holds protect selected supported recovery points against deletion independently of their scheduled retention expiration. They are distinct from AWS Backup Vault Lock, which enforces retention constraints. An ordinary backup schedule does not by itself establish a legal hold, and preserving a backup does not freeze changes in the source application.

File-system lifecycle and backup policies also require careful interpretation. Amazon EFS Lifecycle policies move eligible files between storage classes; they do not establish legal holds. Amazon FSx for Lustre supports native backups for eligible persistent file systems, but not for scratch file systems or file systems linked to S3 data repositories. Select a supported preservation approach for the actual configuration. Exporting relevant data to S3 and protecting the resulting object versions is one option, not a universal requirement; verify that the capture includes the required content and metadata.

A practical preservation design separates application permissions from hold administration, records hold changes, verifies coverage, and periodically tests retrieval. Protect encryption keys and supporting metadata because undeletable ciphertext can still become unusable if its key is destroyed. Preserve integrity information and provenance needed for evidentiary review. Budget for indefinite storage, backup granularity, and archive retrieval costs. Encryption, versioning, ordinary backups, and access policies support preservation, but none alone establishes a complete legal-hold process.

Learn Legal Holds in lessons

6 short lessons on Legal Holds in 3 certification courses.

Open the lessons