Access management in Network Load Balancer
In this section, you will learn:
- Resources you can assign a role for.
- Roles this service has.
- What roles are required for specific actions.
Access management
Yandex Identity and Access Management checks all operations in Yandex Cloud. If an entity does not have required permissions, IAM returns an error.
To grant permissions for a resource, assign the relevant resource roles to an entity performing operations. You can assign roles to a Yandex account, service account, local user, federated user, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.
To assign roles for a resource, you need to have one of the following roles for that resource:
adminresource-manager.adminorganization-manager.adminresource-manager.clouds.ownerorganization-manager.organizations.owner
Resources you can assign a role for
You can assign a role to an organization, cloud, or folder. The roles assigned to organizations, clouds, and folders also apply to their nested resources.
Roles this service has
The chart below shows service’s roles and their permission inheritance. For example, editor inherits all viewer permissions. You can find role descriptions below 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.editor
The load-balancer.editor 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. The role does not allow creating public 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 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.
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.editor 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.
viewer
The viewer role grants the permissions to read the info on any Yandex Cloud resources.
This role 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 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 includes the editor permissions.
Instead of primitive roles, we recommend using service roles with more granular access control, allowing you to implement the least privilege principle.
For more information about primitive roles, see the Yandex Cloud role reference.
What roles do I need
The table below lists the roles required for specific actions. You can always assign a role with more permissions. 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 hosting target groups, you may have the vpc.publicAdmin role instead. To manage the internal network load balancer, you need the load-balancer.privateAdmin role and to manage its target groups, the load-balancer.privateAdmin or compute.admin role.
To manage target groups in subnets lacking the specified administrative roles, you need the vpc.user role for those subnets.
| Action | Methods | Required roles |
|---|---|---|
| Viewing data | ||
| Viewing resource details | get, list, listOperations |
viewer for the resource |
| Managing network load balancers | ||
| Creating and updating load balancers in a folder | create |
load-balancer.privateAdmin / load-balancer.admin or editor for the folder and, if the load balancer is public, networks hosting the target groups. |
| Deleting load balancers | update, delete |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Attaching target groups | attachTargetGroup |
load-balancer.privateAdmin / load-balancer.admin or editor for the folder and, if the load balancer is public, networks hosting target groups. |
| Detaching target groups | detachTargetGroup |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Getting the target group status | getTargetStates |
load-balancer.viewer or viewer for the load balancer and specified target groups |
| Adding and removing listeners | addListener, removeListener |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Stopping and starting a load balancer | stop, start |
load-balancer.privateAdmin / load-balancer.admin or editor for the load balancer |
| Managing target groups | ||
| Creating and updating target groups in a folder | create |
load-balancer.privateAdmin / load-balancer.admin or editor for the folder and subnets hosting the target groups |
| Deleting target groups | update, delete |
load-balancer.privateAdmin / load-balancer.admin or editor for the target group and the load balancer |
| Adding targets to a target group | addTargets |
load-balancer.privateAdmin / load-balancer.admin or editor for the target group, load balancer, and subnets hosting the target groups |
| Removing targets from a target group | removeTargets |
load-balancer.privateAdmin / load-balancer.admin or editor for the target group |
| Resource access management | ||
| Granting, revoking, and viewing roles for a resource | setAccessBindings, updateAccessBindings, listAccessBindings |
admin for the resource |