Configuring snapshot schedule access permissions
To grant a user, group, or service account access to a disk snapshot schedule, assign a role for it.
Assigning a role
- In the management console
, select the folder the schedule belongs to. - Select Compute Cloud.
- In the left-hand panel, select
Snapshots. - Go to the Snapshot schedules tab.
- Select the schedule from the list.
- Go to the
Access bindings tab. - Click Assign bindings.
- In the window that opens, select the group, user, or service account you want to grant access to the schedule.
- Click
Add role and select the required roles. - Click Save.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder through the --folder-name
or --folder-id
parameter.
-
See the description of the CLI command for assigning a role for a disk snapshot schedule:
yc compute snapshot-schedule add-access-binding --help
-
Get a list of schedules in the default folder:
yc compute snapshot-schedule list
Result:
+----------------------+-----------------+--------+-------------+ | ID | NAME | STATUS | DESCRIPTION | +----------------------+-----------------+--------+-------------+ | fd85vvoeea6u******** | first-schedule | ACTIVE | | | fd14ogykea8j******** | second-schedule | ACTIVE | | +----------------------+-----------------+--------+-------------+
-
View a list of roles already assigned for the resource in question:
yc compute snapshot-schedule list-access-bindings <schedule_ID>
-
Assign the role using this command:
-
To a user:
yc compute snapshot-schedule add-access-binding <schedule_ID> \ --user-account-id <user_ID> \ --role <role>
Where:
-
To a service account:
yc compute snapshot-schedule add-access-binding <schedule_ID> \ --service-account-id <service_account_ID> \ --role <role>
Where:
--service-account-id
: Service account ID.--role
: Role to assign.
-
With Terraform
Terraform is distributed under the Business Source License
For more information about the provider resources, see the documentation on the Terraform
If you don't have Terraform, install it and configure the Yandex Cloud provider.
To assign a role for a schedule using Terraform:
-
In the Terraform configuration file, define the parameters of the resources you want to create:
resource "yandex_compute_snapshot_schedule_iam_binding" "sa-access" { snapshot_schedule_id = "<schedule_ID>" role = "<role>" members = ["<subject_type>:<subject_ID>","<subject_type>:<subject_ID>"] }
Where:
snapshot_schedule_id
: Schedule ID.role
: Role to assign.members
: List of types and IDs of subjects getting the role. Specify it asuserAccount:<user_ID>
orserviceAccount:<service_account_ID>
.
For more information about the
yandex_compute_snapshot_schedule_iam_binding
resource parameters, see the relevant provider documentation . -
Create the resources:
-
In the terminal, change to the folder where you edited the configuration file.
-
Make sure the configuration file is correct using the command:
terraform validate
If the configuration is correct, the following message is returned:
Success! The configuration is valid.
-
Run the command:
terraform plan
The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.
-
Apply the configuration changes:
terraform apply
-
Confirm the changes: type
yes
in the terminal and press Enter.
Terraform will create all the required resources. You can check the new resources using the management console
or this CLI command:yc compute snapshot-schedule list-access-bindings <schedule_ID>
-
Use the updateAccessBindings REST API method for the SnapshotSchedule resource or the SnapshotSchedule/UpdateAccessBindings gRPC API call. In the request body, set the action
property to ADD
and specify the user type and ID under subject
.
Assigning multiple roles
- In the management console
, select the folder the schedule belongs to. - Select Compute Cloud.
- In the left-hand panel, select
Snapshots. - Go to the Snapshot schedules tab.
- Select the schedule from the list.
- Go to the
Access bindings tab. - Click Assign bindings.
- In the window that opens, select the group, user, or service account you want to grant access to the schedule.
- Click
Add role and select the required roles. - To add another role, click Add role.
- Click Save.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder through the --folder-name
or --folder-id
parameter.
You can assign multiple roles using the set-access-bindings
command.
Alert
The set-access-bindings
command completely rewrites access permissions for the resource. All current roles for the resource will be deleted.
-
Make sure the resource has no roles assigned that you would not want to lose:
yc compute snapshot-schedule list-access-bindings <schedule_ID>
-
See the description of the CLI command for assigning roles for a disk snapshot schedule:
yc compute snapshot-schedule set-access-bindings --help
-
Assign roles:
yc compute snapshot-schedule set-access-bindings <schedule_ID> \ --access-binding role=<role>,subject=<subject_type>:<subject_ID>
Where:
-
--access-binding
: Role to assign:role
: ID of the role to assign.subject
: Type and ID of the subject getting the role.
For example, this command will assign roles to multiple users and a single service account:
yc compute snapshot-schedule set-access-bindings my-schedule \ --access-binding role=editor,subject=userAccount:gfei8n54hmfh******** --access-binding role=viewer,subject=userAccount:helj89sfj80a******** --access-binding role=editor,subject=serviceAccount:ajel6l0jcb9s********
-
If you don't have Terraform, install it and configure the Yandex Cloud provider.
To assign multiple roles for a schedule using Terraform:
-
In the Terraform configuration file, define the parameters of the resources you want to create:
resource "yandex_compute_snapshot_schedule_iam_binding" "role-1" { snapshot_schedule_id = "<schedule_ID>" role = "<role_1>" members = ["<subject_type>:<subject_ID>"] } resource "yandex_compute_snapshot_schedule_iam_binding" "role-2" { snapshot_schedule_id = "<schedule_ID>" role = "<role_2>" members = ["<subject_type>:<subject_ID>"] }
Where:
snapshot_schedule_id
: Schedule ID.role
: Role to assign.members
: List of types and IDs of subjects getting the role. Specify it asuserAccount:<user_ID>
orserviceAccount:<service_account_ID>
.
For more information about the
yandex_compute_snapshot_schedule_iam_binding
resource parameters, see the relevant provider documentation . -
Create the resources:
-
In the terminal, change to the folder where you edited the configuration file.
-
Make sure the configuration file is correct using the command:
terraform validate
If the configuration is correct, the following message is returned:
Success! The configuration is valid.
-
Run the command:
terraform plan
The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.
-
Apply the configuration changes:
terraform apply
-
Confirm the changes: type
yes
in the terminal and press Enter.
You can check the updates using the management console
or this CLI command:yc compute snapshot-schedule list-access-bindings <schedule_ID>
-
Use the setAccessBindings REST API method for the SnapshotSchedule resource or the SnapshotSchedule/SetAccessBindings gRPC API call.
Revoking a role
- In the management console
, select the folder the schedule belongs to. - Select Compute Cloud.
- In the left-hand panel, select
Snapshots. - Go to the Snapshot schedules tab.
- Select the schedule from the list.
- Go to the
Access bindings tab. - In the line with the user in question, click
and select Edit roles. - Click
next to a role to delete it. - Click Save.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder through the --folder-name
or --folder-id
parameter.
-
See the description of the CLI command for revoking a role for a disk snapshot schedule:
yc compute snapshot-schedule remove-access-binding --help
-
View the roles and assignees for the resource:
yc compute snapshot-schedule list-access-bindings <schedule_ID>
-
To revoke access permissions, run this command:
yc compute snapshot-schedule remove-access-binding <schedule_ID> \ --role <role_ID> \ --subject <subject_type>:<subject_ID>
Where:
--role
: ID of the role to revoke.--subject
: Subject to revoke the role from.
For example, this command revokes the
viewer
role for the schedule from a user with theajel6l0jcb9s********
ID:yc compute snapshot-schedule remove-access-binding my-schedule \ --role viewer \ --subject userAccount:ajel6l0jcb9s********
If you don't have Terraform, install it and configure the Yandex Cloud provider.
To revoke a role assigned for a disk snapshot schedule using Terraform:
-
Open the Terraform configuration file and delete the section specifying the role:
... resource "yandex_compute_snapshot_schedule_iam_binding" "sa-access" { snapshot_schedule_id = "<schedule_ID>" role = "<role>" members = ["<subject_type>:<subject_ID>"] }
-
Apply the changes:
-
In the terminal, change to the folder where you edited the configuration file.
-
Make sure the configuration file is correct using the command:
terraform validate
If the configuration is correct, the following message is returned:
Success! The configuration is valid.
-
Run the command:
terraform plan
The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.
-
Apply the configuration changes:
terraform apply
-
Confirm the changes: type
yes
in the terminal and press Enter.
You can check the updates using the management console
or this CLI command:yc compute snapshot-schedule list-access-bindings <schedule_ID>
-
To revoke roles for a disk snapshot schedule, use the [updateAccessBindings](../../api-ref/SnapshotSchedule /updateAccessBindings.md) REST API method for the SnapshotSchedule resource or the SnapshotScheduleService/UpdateAccessBindings gRPC API call. In the request body, set the action
property to REMOVE
and specify the user type and ID under subject
.