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
I would like to request the addition of a "AWS Snapshot Lock" feature to Barman. This feature would help protect snapshots against accidental or malicious deletions and allow them to be stored in a write-once-read-many (WORM) format for a specific duration. While a snapshot is locked, it can’t be deleted by any user, regardless of their permissions. However, users can continue to use a locked snapshot as they would use any other snapshot.
Use Cases
Protect snapshots from being accidentally deleted by administrators or automated processes.
Ensure snapshots are stored in a tamper-proof state for compliance with regulations requiring data immutability.
Implement retention policies to automatically manage the lifecycle of snapshots.
We looking at adding WORM support (ransomware protection) for local backups (as long as the underlying FS has some kind of WORM functionality) and we'll have a look at this feature for snapshots as well.
Hi,
I would like to request the addition of a "AWS Snapshot Lock" feature to Barman. This feature would help protect snapshots against accidental or malicious deletions and allow them to be stored in a write-once-read-many (WORM) format for a specific duration. While a snapshot is locked, it can’t be deleted by any user, regardless of their permissions. However, users can continue to use a locked snapshot as they would use any other snapshot.
Use Cases
Example Command Line Interface:
The other two supported would be:
--aws-snapshot-cool-off-period=1-72_hours
and--snapshot-expiration-date=YYYY-MM-DDThh:mm:ss.sssZ
, mutually exclusive.The text was updated successfully, but these errors were encountered: