You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| snapshotLockExpirationDate | Lock expiration date (RFC3339 format) |
9
+
| snapshotLockCoolOffPeriod | Cool-off period in hours (compliance mode only) |
6
10
7
11
The AWS EBS CSI Driver supports [tagging](tagging.md) through `VolumeSnapshotClass.parameters` (in v1.6.0 and later).
8
12
## Prerequisites
@@ -44,6 +48,49 @@ parameters:
44
48
45
49
The driver will attempt to check if the availability zones provided are supported for fast snapshot restore before attempting to create the snapshot. If the `EnableFastSnapshotRestores` API call fails, the driver will hard-fail the request and delete the snapshot. This is to ensure that the snapshot is not left in an inconsistent state.
46
50
51
+
# Snapshot Lock
52
+
53
+
The EBS CSI Driver provides support for [EBS Snapshot Lock](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshot-lock.html) via `VolumeSnapshotClass.parameters`. Snapshot locking protects snapshots from accidental or malicious deletion. A locked snapshot can't be deleted.
54
+
55
+
Snapshot locking supports two modes:
56
+
-**Governance mode**: Allows privileged users to unlock snapshots
57
+
-**Compliance mode**: Prevents unlocking until expiration (with optional cool-off period)
58
+
59
+
Lock duration can be specified using either:
60
+
-`snapshotLockDuration`: Duration in days
61
+
-`snapshotLockExpirationDate`: Specific expiration date in RFC3339 format
62
+
63
+
**Example - Governance Mode with Duration**
64
+
```yaml
65
+
apiVersion: snapshot.storage.k8s.io/v1
66
+
kind: VolumeSnapshotClass
67
+
metadata:
68
+
name: csi-aws-vsc-locked
69
+
driver: ebs.csi.aws.com
70
+
deletionPolicy: Delete
71
+
parameters:
72
+
snapshotLockMode: "governance"
73
+
snapshotLockDuration: "7"
74
+
```
75
+
76
+
**Example - Compliance Mode with Expiration Date**
If the `LockSnapshot` API call fails, the driver will hard-fail the request and delete the snapshot. This ensures that the snapshot is not left in an unlocked state when locking was explicitly requested.
0 commit comments