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 permission for a resource, assign roles for this resource to the subject that will perform operations. Roles can be assigned to a Yandex account, a service account, federated users, a user group, or a system group. For more information, see How access management works in Yandex Cloud.
Only users with the admin
, resource-manager.clouds.owner
, or organization-manager.organizations.owner
role for a resource can assign roles for this resource.
Which resources you can assign a role for
As with other services, you can assign roles for clouds, folder and service accounts. The roles assigned for clouds and 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 you to get lists of target groups and network load balancers, details on them and their operations, and view information about the cloud, cloud limits, and the folder.
load-balancer.viewer
The load-balancer.viewer
role lets you view resource model objects.
load-balancer.privateAdmin
The load-balancer.privateAdmin
role lets you create, update, and delete load balancers and target groups without granting access to them from the internet.
load-balancer.admin
The load-balancer.admin
role lets you create both private and public load balancers.
Primitive roles
auditor
Grants permission to view service configuration and metadata without access to data.
viewer
Enables you to view information about resources.
editor
Allows you to manage resources, e.g., create, edit, and delete them.
admin
Allows you to manage your resources and access to them.
For more information about primitive roles, see Roles.
What roles do I need
The table below lists the roles needed to perform a particular action. You can always assign a role granting more permissions than the role specified. For example, you can assign the editor
role instead of the viewer
one.
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 |