Access management in Network Load Balancer
In this section, you will learn:
- Which resources you can assign a role for.
- Which roles exist in the service.
- Which roles are required for particular actions.
About access management
In Yandex Cloud, all transactions are checked in Yandex Identity and Access Management. If a subject does not have the required permission, the service returns an error.
To grant permissions for a resource, assign roles for this resource to the subject that will perform the operations. You can assign roles to a Yandex account, service account, federated users, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.
Roles for a resource can be assigned by users who have at least one of the following roles for that resource:
adminresource-manager.adminorganization-manager.adminresource-manager.clouds.ownerorganization-manager.organizations.owner
Which resources you can assign a role for
You can assign a role to an organization, cloud, or folder. The roles assigned for organizations, clouds, or folders also apply to nested resources.
Which roles exist in the service
The chart below shows which roles are available in the service and how they inherit each other's permissions. For example, the editor role includes all the permissions of viewer. You can find the description of each role under the chart.
Service roles
load-balancer.auditor
The load-balancer.auditor role enables viewing the list of target groups and network load balancers, as well as viewing the info on them and on the Network Load Balancer quotas.
Users with this role can:
- View the list of target groups and the info on them.
- View the list of network load balancers and the info on them.
- View the list of operations with the Network Load Balancer resources.
- View information on the relevant cloud and folder.
- View info on Network Load Balancer quotas.
load-balancer.viewer
The load-balancer.viewer role enables viewing the list of target groups and network load balancers, as well as viewing the info on them, the list of operations on them, the info on the relevant cloud and folder, and the Network Load Balancer quotas.
Users with this role can:
- View the list of target groups and the info on them.
- View the list of network load balancers and the info on them.
- View the list of operations with the Network Load Balancer resources.
- View information on the relevant cloud and folder.
- View info on Network Load Balancer quotas.
This role includes the load-balancer.auditor permissions.
load-balancer.privateAdmin
The load-balancer.privateAdmin role enables managing internal network load balancers and target groups, as well as viewing info on them and on the cloud networks, subnets, route tables, gateways, security groups, and IP addresses.
Users with this role can:
- View the list of network load balancers and the info on them, as well as create internal network load balances (including those with UDP listeners), modify, delete, start, and stop them.
- View the list of target groups and the info on them, as well as create, modify, delete, and use target groups.
- View the list of cloud networks and the info on them.
- View the list of subnets and info on them, as well as use them.
- View the list of cloud resource addresses and the info on them.
- View the list of route tables and the info on them.
- View the list of security groups and the info on them.
- View information on NAT gateways.
- View the info on the used IP addresses in subnets, as well as create internal addresses.
- View the info on operations with the Virtual Private Cloud and Compute Cloud resources.
- View the list of operations with the Network Load Balancer resources.
- View information on the relevant cloud and folder.
- View info on Network Load Balancer and Virtual Private Cloud quotas.
This role includes the load-balancer.viewer and vpc.viewer permissions.
load-balancer.admin
The load-balancer.admin role enables managing internal and external network load balancers and target groups, as well as viewing info on them and on the cloud networks, subnets, route tables, gateways, security groups, and IP addresses.
Users with this role can:
- View the list of network load balancers and info on them.
- Create internal and external network load balancers and those with UDP listeners, as well as modify, delete, start, and stop load balancers.
- View the list of target groups and the info on them, as well as create, modify, delete, and use target groups.
- View the list of cloud networks and info on them, as well as set up external access to them.
- View the list of subnets and info on them, as well as use them.
- View the list of cloud resource addresses and the info on them.
- View the list of route tables and the info on them.
- View the list of security groups and the info on them.
- View information on NAT gateways.
- View the info on the used IP addresses, create private and public addresses, and use them.
- View the info on operations with the Virtual Private Cloud and Compute Cloud resources.
- View the list of operations with the Network Load Balancer resources.
- View information on the relevant cloud and folder.
- View info on Network Load Balancer and Virtual Private Cloud quotas.
This role includes the load-balancer.privateAdmin permissions.
Primitive roles
Primitive roles allow users to perform actions in all Yandex Cloud services.
auditor
The auditor role grants a permission to read configuration and metadata of any Yandex Cloud resources without any access to data.
For instance, users with this role can:
- View info on a resource.
- View the resource metadata.
- View the list of operations with a resource.
auditor is the most secure role that does not grant any access to the service data. This role suits the users who need minimum access to the Yandex Cloud resources.
Currently, the auditor role is available for all Yandex Cloud services, except for:
- Yandex Data Streams
- Yandex Query
viewer
The viewer role grants the permissions to read the info on any Yandex Cloud resources.
This role also includes the auditor permissions.
Unlike auditor, the viewer role provides access to service data in read mode.
editor
The editor role provides permissions to manage any Yandex Cloud resources, except for assigning roles to other users, transferring organization ownership, removing an organization, and deleting Key Management Service encryption keys.
For instance, users with this role can create, modify, and delete resources.
This role also includes the viewer permissions.
admin
The admin role enables assigning any roles, except for resource-manager.clouds.owner and organization-manager.organizations.owner, and provides permissions to manage any Yandex Cloud resources (except for transferring organization ownership and removing an organization).
Prior to assigning the admin role for an organization, cloud, or billing account, make sure to check out the information on protecting privileged accounts.
This role also includes the editor permissions.
Instead of primitive roles, we recommend using service roles. This ensures more selective access control and implementation of the principle of least privilege.
For more information about primitive roles, see the Yandex Cloud role reference.
What roles do I need
The table below lists the roles required to perform a particular action. You can always assign a role offering more permissions than the one specified. For example, you can assign the editor role instead of viewer.
Any operations with a network load balancer that has a public IP address require the load-balancer.admin role. In networks where target groups are located, you can have the vpc.publicAdmin role instead. Operations on the internal network load balancer require the load-balancer.privateAdmin role and operations on its target groups, the load-balancer.privateAdmin or compute.admin role.
Operations on target groups located in subnets, where the specified administrative roles are missing, require the vpc.user role for these subnets.
| Action | Methods | Required roles |
|---|---|---|
| View data | ||
| View information about any resource | get, list, listOperations |
viewer for this resource |
| Manage network load balancers | ||
| Create and update load balancers in folders | create |
load-balancer.privateAdmin / load-balancer.admin or editor for the folder and, if the load balancer is public, networks where target groups are located |
| Delete load balancers | update, delete |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Attach target groups | attachTargetGroup |
load-balancer.privateAdmin / load-balancer.admin or editor for the folder and, if the load balancer is public, networks where target groups are located |
| Detach target groups | detachTargetGroup |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Get states of target groups | getTargetStates |
load-balancer.viewer or viewer for the load balancer and the specified target groups |
| Add and remove listeners | addListener, removeListener |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Stop and start a load balancer | stop, start |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Manage target groups | ||
| Create and update target groups in folders | create |
load-balancer.privateAdmin / load-balancer.admin or editor for the folder and subnets where target groups are located |
| Delete target groups | update, delete |
load-balancer.privateAdmin / load-balancer.admin or editor for the target group and load balancer |
| Add resources in a target group | addTargets |
load-balancer.privateAdmin / load-balancer.admin or editor for the target group, load balancer, and subnets where target groups are located |
| Remove resources in a target group | removeTargets |
load-balancer.privateAdmin / load-balancer.admin or editor for the target group |
| Manage resource access | ||
| Grant a role, revoke a role, and view roles granted for the resource | setAccessBindings, updateAccessBindings, listAccessBindings |
admin for the resource |