Control access to Amazon EBS snapshot lock
By default, users don't have permission to work with snapshot locks. To allow users to use snapshot locks, you must create IAM policies that grant permission to use specific resources and API actions. For more information, see Creating IAM policies in the IAM User Guide.
Required permissions
To work with snapshot locks, users need the following permissions.
-
ec2:LockSnapshot— To lock snapshots. -
ec2:UnlockSnapshot— To unlock snapshots. -
ec2:DescribeLockedSnapshots— To view snapshot lock settings.
The following is an example IAM policy that gives users permission to lock and unlock
snapshots, and to view snapshot lock settings. It includes the ec2:DescribeSnapshots
permission for console users. If some permissions are not needed, you can remove them from
the policy.
{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "ec2:LockSnapshot", "ec2:UnlockSnapshot", "ec2:DescribeLockedSnapshots", "ec2:DescribeSnapshots" ] }] }
To provide access, add permissions to your users, groups, or roles:
-
Users and groups in AWS IAM Identity Center:
Create a permission set. Follow the instructions in Create a permission set in the AWS IAM Identity Center User Guide.
-
Users managed in IAM through an identity provider:
Create a role for identity federation. Follow the instructions in Create a role for a third-party identity provider (federation) in the IAM User Guide.
-
IAM users:
-
Create a role that your user can assume. Follow the instructions in Create a role for an IAM user in the IAM User Guide.
-
(Not recommended) Attach a policy directly to a user or add a user to a user group. Follow the instructions in Adding permissions to a user (console) in the IAM User Guide.
-
Restrict access with condition keys
You can use condition keys to restrict how users are allowed to lock snapshots.
ec2:SnapshotLockDuration
You can use the ec2:SnapshotLockDuration condition key to restrict users
to specific lock durations when locking snapshots.
The following example policy restricts users to specifying a lock duration between
10 and 50 days.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "ec2:LockSnapshot", "Resource": "arn:aws:ec2:region::snapshot/*" "Condition": { "NumericGreaterThan" : { "ec2:SnapshotLockDuration" : 10 } "NumericLessThan":{ "ec2:SnapshotLockDuration": 50 } } } ] }
ec2:CoolOffPeriod
You can use the ec2:CoolOffPeriod condition key to prevent users
from locking snapshots in compliance mode without a cooling-off period.
The following example policy restricts users to specifying a cooling-off period
greater than 48 hours when locking snapshots in compliance mode.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "ec2:LockSnapshot", "Resource": "arn:aws:ec2:region::snapshot/*" "Condition": { "NumericGreaterThan": { "ec2:CoolOffPeriod": 48 } } } ] }
