lock_snapshot
async
¶
lock_snapshot(
*,
config_overrides: Optional[AsyncEC2ClientConfig] = None,
snapshot_id: Optional[SnapshotId] = None,
dry_run: Optional[Boolean] = None,
lock_mode: Optional[LockMode] = None,
cool_off_period: Optional[CoolOffPeriodRequestHours] = None,
lock_duration: Optional[RetentionPeriodRequestDays] = None,
expiration_date: Optional[MillisecondDateTime] = None,
) -> LockSnapshotResult
Locks an Amazon EBS snapshot in either governance or compliance mode to protect it against accidental or malicious deletions for a specific duration. A locked snapshot can't be deleted.
You can also use this action to modify the lock settings for a snapshot that is already locked. The allowed modifications depend on the lock mode and lock state:
-
If the snapshot is locked in governance mode, you can modify the lock mode and the lock duration or lock expiration date.
-
If the snapshot is locked in compliance mode and it is in the cooling-off period, you can modify the lock mode and the lock duration or lock expiration date.
-
If the snapshot is locked in compliance mode and the cooling-off period has lapsed, you can only increase the lock duration or extend the lock expiration date.
Parameters:
-
snapshot_id(Optional[SnapshotId], default:None) –The ID of the snapshot to lock.
-
dry_run(Optional[Boolean], default:None) –Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is
DryRunOperation. Otherwise, it isUnauthorizedOperation. -
lock_mode(Optional[LockMode], default:None) –The mode in which to lock the snapshot. Specify one of the following:
-
governance- Locks the snapshot in governance mode. Snapshots locked in governance mode can't be deleted until one of the following conditions are met:-
The lock duration expires.
-
The snapshot is unlocked by a user with the appropriate permissions.
Users with the appropriate IAM permissions can unlock the snapshot, increase or decrease the lock duration, and change the lock mode to
complianceat any time.If you lock a snapshot in
governancemode, omit CoolOffPeriod. -
-
compliance- Locks the snapshot in compliance mode. Snapshots locked in compliance mode can't be unlocked by any user. They can be deleted only after the lock duration expires. Users can't decrease the lock duration or change the lock mode togovernance. However, users with appropriate IAM permissions can increase the lock duration at any time.If you lock a snapshot in
compliancemode, you can optionally specify CoolOffPeriod.
-
-
cool_off_period(Optional[CoolOffPeriodRequestHours], default:None) –The cooling-off period during which you can unlock the snapshot or modify the lock settings after locking the snapshot in compliance mode, in hours. After the cooling-off period expires, you can't unlock or delete the snapshot, decrease the lock duration, or change the lock mode. You can increase the lock duration after the cooling-off period expires.
The cooling-off period is optional when locking a snapshot in compliance mode. If you are locking the snapshot in governance mode, omit this parameter.
To lock the snapshot in compliance mode immediately without a cooling-off period, omit this parameter.
If you are extending the lock duration for a snapshot that is locked in compliance mode after the cooling-off period has expired, omit this parameter. If you specify a cooling-period in a such a request, the request fails.
Allowed values: Min 1, max 72.
-
lock_duration(Optional[RetentionPeriodRequestDays], default:None) –The period of time for which to lock the snapshot, in days. The snapshot lock will automatically expire after this period lapses.
You must specify either this parameter or ExpirationDate, but not both.
Allowed values: Min: 1, max 36500
-
expiration_date(Optional[MillisecondDateTime], default:None) –The date and time at which the snapshot lock is to automatically expire, in the UTC time zone (
YYYY-MM-DDThh:mm:ss.sssZ).You must specify either this parameter or LockDuration, but not both.
Raises:
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_ec2/_services/async_ec2.py
49442 49443 49444 49445 49446 49447 49448 49449 49450 49451 49452 49453 49454 49455 49456 49457 49458 49459 49460 49461 49462 49463 49464 49465 49466 49467 49468 49469 49470 49471 49472 49473 49474 49475 49476 49477 49478 49479 49480 49481 49482 49483 49484 49485 49486 49487 49488 49489 49490 49491 49492 49493 49494 49495 49496 49497 49498 49499 49500 49501 49502 49503 49504 49505 49506 49507 49508 49509 49510 49511 | |