Access management in Cloud DNS
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 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 dns.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 DNS zone through the YC CLI or Yandex Cloud API.
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
dns.auditor
The dns.auditor
role enables viewing info on DNS zones and access permissions assigned to them, as well as on the relevant folder and Cloud DNS quotas. This role does not provide access to resource records.
dns.viewer
The dns.viewer
role enables viewing info on DNS zones and access permissions assigned to them, as well as on the resource records, the relevant folder, and Cloud DNS quotas.
This role also includes the dns.auditor
permissions.
dns.editor
The dns.editor
role enables managing DNS zones and resource records, as well as viewing info on the relevant folder and Cloud DNS quotas.
Users with this role can:
- View information on DNS zones as well as create, use, modify, and delete them.
- View information on resource records as well as create, modify, and delete them.
- Create nested public DNS zones.
- View information on access permissions assigned for DNS zones.
- View information on Cloud DNS quotas.
- View information on the relevant folder.
This role also includes the dns.viewer
permissions.
dns.admin
The dns.admin
role enables managing DNS zones and access to them, and resource records, as well as viewing info on the relevant folder and Cloud DNS quotas.
Users with this role can:
- View information on access permissions assigned for DNS zones, as well as create, modify, and delete such permissions.
- View information on DNS zones as well as create, use, modify, and delete them.
- View information on resource records as well as create, modify, and delete them.
- Create nested public DNS zones.
- View information on Cloud DNS quotas.
- View information on the relevant folder.
This role also includes the dns.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 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.
What roles do I need
The table below lists the roles required to perform a particular action. You can always assign a role offering more permissions than the one specified. For example, assign editor
instead of viewer
or dns.admin
instead of dns.editor
.
Action | Methods | Required roles |
---|---|---|
Viewing metadata | ||
Viewing information about DNS zones | get , list |
dns.auditor for this resource |
View data | ||
Viewing information about DNS zones and their resource records | get , list , listRecordSets |
viewer or dns.viewer for the resource in question |
Manage DNS zones | ||
Create a zone | create |
editor or dns.editor for the folder as well as vpc.user for the folder and the VPC network if it is an internal zone |
Edit and delete zones | update , delete |
editor or dns.editor for the folder as well as vpc.user for the folder and the VPC network if it is an internal zone |
Creating subzones | create |
editor or dns.editor for the folder housing the zone that will include the subzones being created as well as vpc.user for this folder or VPC network if it is an internal zone |
Manage resource records | ||
Create resource records in a DNS zone | create |
editor or dns.editor for the folder or zone |
Edit and delete resource records | update , delete |
editor or dns.editor |
Manage access to DNS zones | ||
Grant a role, revoke a role, and view roles granted for DNS zones | setAccessBindings , updateAccessBindings , listAccessBindings |
admin or dns.admin for the folder or zone |
To restrict user access, assign users roles for individual zones or subzones.