Configuring access permissions for a dedicated host group

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id.

If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. See the description of the CLI command for assigning a role for a dedicated host group:

   yc compute host-group add-access-binding --help
   

2. Get a list of dedicated host groups in the default folder:

   yc compute host-group list
   

3. View the list of roles already assigned for the resource:

   yc compute host-group list-access-bindings <dedicated_host_group_name_or_ID>
   

4. Assign a role using this command:

   yc compute host-group add-access-binding <dedicated_host_group_name_or_ID> \
     --role <role> \
     --subject <subject_type>:<subject_ID>
   

   Where:

   • --role: Role.

   • --subject: Subject getting the role.

     Subject designations

     To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

     Subject type	Subject designation	Yandex Cloud CLI parameter
     userAccount	userAccount:<user_ID>	--user-account-id or --user-yandex-login
     serviceAccount	serviceAccount:<service_account_ID>	--service-account-id or --service-account-name
     federatedUser	federatedUser:<user_ID>	--user-account-id
     group	group:<group_ID>	--group-members
     system	system:allAuthenticatedUsers (All authenticated users group)	--all-authenticated-users
     	system:allUsers (All users group)	—
     	system:group:organization:<organization_ID>:users (All users in organization X group)	--organization-users
     	system:group:federation:<federation_ID>:users (All users in federation N group)	--federation-users
     	system:group:userpool:<pool_ID>:users (All users in userpool P group)	—

To assign a role, use the updateAccessBindings REST API method for the HostGroup resource or the HostGroupService/UpdateAccessBindings gRPC API call. In the request body, set the action property to ADD and specify the subject type and ID under subject.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id.

If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

You can assign multiple roles using the set-access-bindings command.

1. Make sure the resource has no roles assigned that you would not want to lose:

   yc compute host-group list-access-bindings <dedicated_host_group_name_or_ID>
   

2. See the description of the CLI command for assigning roles for a dedicated host group:

   yc compute host-group set-access-bindings --help
   

3. Assign roles:

   yc compute host-group set-access-bindings <dedicated_host_group_name_or_ID> \
     --access-binding role=<role>,subject=<subject_type>:<subject_ID> \
     --access-binding role=<role>,subject=<subject_type>:<subject_ID>
   

   Where --access-binding contains access permission settings:

   • role: Role.

   • subject: Subject getting the role.

     Indicating a subject

     To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

     Subject type	Subject designation	Yandex Cloud CLI parameter
     userAccount	userAccount:<user_ID>	--user-account-id or --user-yandex-login
     serviceAccount	serviceAccount:<service_account_ID>	--service-account-id or --service-account-name
     federatedUser	federatedUser:<user_ID>	--user-account-id
     group	group:<group_ID>	--group-members
     system	system:allAuthenticatedUsers (All authenticated users group)	--all-authenticated-users
     	system:allUsers (All users group)	—
     	system:group:organization:<organization_ID>:users (All users in organization X group)	--organization-users
     	system:group:federation:<federation_ID>:users (All users in federation N group)	--federation-users
     	system:group:userpool:<pool_ID>:users (All users in userpool P group)	—

   For example, assign roles to several users and one service account:

   yc compute host-group set-access-bindings my-host-group \
     --access-binding role=editor,subject=userAccount:gfei8n54hmfh******** \
     --access-binding role=viewer,subject=userAccount:helj89sfj80a******** \
     --access-binding role=editor,subject=serviceAccount:ajel6l0jcb9s********
   

To assign roles for a dedicated host group, use the setAccessBindings REST API method for the HostGroup resource or the HostGroupService/SetAccessBindings gRPC API call. In the request body, specify the subject type and ID under subject.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id.

If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. See the description of the CLI command for revoking a role for for a dedicated host group:

   yc compute host-group remove-access-binding --help
   

2. View the list of users and their roles for the resource:

   yc compute host-group list-access-bindings <dedicated_host_group_name_or_ID>
   

3. To revoke access permissions, run this command:

   yc compute host-group remove-access-binding <dedicated_host_group_name_or_ID> \
     --role=<role> \
     --subject=<subject_type>:<subject_ID>
   

   Where:

   • --role: ID of the role you need to revoke.

   • --subject: Subject to revoke the role from.

     Subject designations

     To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

     Subject type	Subject designation	Yandex Cloud CLI parameter
     userAccount	userAccount:<user_ID>	--user-account-id or --user-yandex-login
     serviceAccount	serviceAccount:<service_account_ID>	--service-account-id or --service-account-name
     federatedUser	federatedUser:<user_ID>	--user-account-id
     group	group:<group_ID>	--group-members
     system	system:allAuthenticatedUsers (All authenticated users group)	--all-authenticated-users
     	system:allUsers (All users group)	—
     	system:group:organization:<organization_ID>:users (All users in organization X group)	--organization-users
     	system:group:federation:<federation_ID>:users (All users in federation N group)	--federation-users
     	system:group:userpool:<pool_ID>:users (All users in userpool P group)	—

   For example, this command revokes the viewer role for the dedicated host group from a user with the ajel6l0jcb9s******** ID:

   yc compute host-group remove-access-binding my-host-group \
     --role viewer \
     --subject userAccount:ajel6l0jcb9s********
   

To revoke a role, use the updateAccessBindings REST API method for the HostGroup resource or the HostGroupService/UpdateAccessBindings gRPC API call. In the request body, set the action property to REMOVE and specify the subject type and ID under subject.