Access management in Application 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
alb.auditor
The alb.auditor
role enables you to view a list of Application Load Balancer resources and their metadata.
alb.viewer
The alb.viewer
role lets you view resource model objects.
Includes all permissions granted by the alb.auditor
role.
alb.user
The alb.user
role allows using Application Load Balancer resources. It is assigned for a folder. For example, with this role you can use Application Load Balancer resources of one folder in Application Load Balancer resources of another folder.
Includes all permissions granted by the alb.viewer
role.
alb.editor
The alb.editor
role lets you view, create, update, and delete resource model objects.
Includes all permissions granted by the alb.user
role.
alb.admin
The alb.admin
role lets you manage Application Load Balancer: view, create, update, and delete resources, as well as manage access to them (this feature is currently unavailable).
Includes all permissions granted by the alb.editor
role.
Note
To connect a public IP address to a new or existing L7 load balancer, you need to assign the vpc.publicAdmin
role to the network where the load balancer is located, apart from the alb.editor
or alb.admin
roles.
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.
Action | Methods | Required roles |
---|---|---|
View data | ||
View information about any resource | get , list , listOperations |
alb.viewer for this resource |
Manage L7 load balancers | ||
Create and update L7 load balancers with public IP addresses | create |
alb.editor and vpc.publicAdmin to the network where the load balancer is located |
Create and update L7 load balancers without a public IP address | create |
alb.editor |
Delete L7 load balancers | update , delete |
alb.editor |
Get the status of target groups | getTargetStates |
alb.viewer |
Add, update, and remove listeners | addListener , updateListener , removeListener |
alb.editor |
Add, update, and remove an SNI match | addSniMatch , updateSniMatch , removeSniMatch |
alb.editor |
Stop and start an L7 load balancer | stop , start |
alb.editor |
Manage HTTP routers | ||
Create an HTTP router | create |
alb.editor |
Update an HTTP router | update |
alb.editor |
Delete an HTTP router | delete |
alb.editor |
Manage backend groups | ||
Create and update backend groups | create , update , updateBackend |
alb.editor |
Delete backend groups | delete |
alb.editor |
Add resources in a backend group | addBackend |
alb.editor |
Remove resources in a backend group | removeBackend |
alb.editor |
Manage target groups | ||
Create and update target groups in a folder | create , update |
alb.editor |
Delete target groups | delete |
alb.editor |
Add resources in a target group | addTargets |
alb.editor |
Remove resources in a target group | removeTargets |
alb.editor |
Manage resource access | ||
Grant a role, revoke a role, and view roles granted for the resource | setAccessBindings , updateAccessBindings , listAccessBindings |
admin for the resource |