Access management in Serverless Containers
Serverless Containers uses roles to manage access rights.
In this section, you will learn:
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 the serverless-containers.admin
role or one of the following roles for that resource:
admin
resource-manager.admin
organization-manager.admin
resource-manager.clouds.owner
organization-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.
You can assign a role for a container via the YC CLI or Yandex Cloud API.
Which roles exist in the service
The list below shows all roles considered when verifying access permissions in Serverless Containers.
Service roles
serverless-containers.auditor
The serverless-containers.auditor
role enables viewing info on containers, except for the info on the revision environment variables.
serverless-containers.viewer
The serverless-containers.viewer
role enables viewing info on containers, as well as on the relevant cloud and folder.
Users with this role can:
- View info on containers, including the revision environment variables.
- View info on granted access permissions to containers.
- View info on the relevant cloud.
- View info on the relevant folder.
This role also includes the serverless-containers.auditor
permissions.
serverless-containers.editor
The serverless-containers.editor
role enables managing containers and viewing info on them, as well as on the relevant cloud and folder.
Users with this role can:
- Create, invoke, modify, and delete containers.
- View info on containers, including the revision environment variables, as well as on the granted access permissions to containers.
- View info on the relevant cloud.
- View info on the relevant folder.
This role also includes the serverless-containers.viewer
permissions.
serverless-containers.admin
The serverless-containers.admin
role enables managing containers and access to them, as well as viewing info on containers and the relevant cloud and folder.
Users with this role can:
- Create, invoke, modify, and delete containers.
- View info on granted access permissions to containers and modify such permissions.
- View info on containers, including the revision environment variables.
- View info on the relevant cloud.
- View info on the relevant folder.
This role also includes the serverless-containers.editor
permissions.
serverless-containers.containerInvoker
The serverless-containers.containerInvoker
role enables invoking containers.
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.