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 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
dns.auditor
The dns.auditor
role enables viewing info on DNS zones and access bindings 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 bindings 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 bindings 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 bindings for DNS zones, as well as create, modify, and delete such bindings.
- 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
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, 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.