Access management in Managed Service for GitLab
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.
To use the service, log in to the management console with a Yandex account or federated account.
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 gitlab.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 for an organization, cloud, or folder. Their nested resources will automatically inherit the roles.
Which roles exist in the service
Service roles
gitlab.auditor
The gitlab.auditor
role enables viewing info on the Managed Service for GitLab instances and quotas.
gitlab.viewer
The gitlab.viewer
role enables viewing info on the Managed Service for GitLab instances and quotas.
This role includes the gitlab.auditor
permissions.
gitlab.editor
The gitlab.editor
role enables managing the Managed Service for GitLab instances and migrating them to other availability zones.
Users with this role can:
- View info on the Managed Service for GitLab instances, as well as create, modify, and delete such instances.
- Migrate instances to another availability zones.
- View info on the quotas for Managed Service for GitLab.
This role includes the gitlab.viewer
permissions.
To create Managed Service for GitLab instances, you also need the vpc.user
role.
gitlab.admin
The gitlab.admin
role enables managing the Managed Service for GitLab instances and migrating them to other availability zones.
Users with this role can:
- View info on the Managed Service for GitLab instances, as well as create, modify, and delete such instances.
- Migrate instances to another availability zones.
- View info on the quotas for Managed Service for GitLab.
This role includes the gitlab.editor
permissions.
To create Managed Service for GitLab instances, you also need the vpc.user
role.
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.
Roles required
To use the service, you need the gitlab.editor role or higher to the folder where the projects are being created. With the gitlab.viewer
role, you can only view the list of the projects and the contents of uploaded files.
To create a Managed Service for GitLab instance, you need the vpc.user role and the gitlab.editor
role or higher.
You can always assign a role with more permissions. For instance, you can assign gitlab.admin
instead of gitlab.editor
.