Access management in Managed Service for Apache Kafka®
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.
To allow access to Managed Service for Apache Kafka® service resources (clusters and hosts, cluster backups, partitions and topics, and users), assign the user the appropriate roles for the folder or cloud hosting the 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
managed-kafka.auditor
The managed-kafka.auditor
role allows you to view information about Apache Kafka® clusters, as well as quotas and resource operations for Managed Service for Apache Kafka®.
managed-kafka.viewer
The managed-kafka.viewer
role allows you to view information about Apache Kafka® clusters and their logs, as well as information on quotas and resource operations for Managed Service for Apache Kafka®.
This role includes the permissions of the managed-kafka.auditor
role.
managed-kafka.editor
The managed-kafka.editor
role allows you to manage Apache Kafka® clusters and view their logs, as well as get information about quotas and service resource operations.
Users with this role can:
- View information about Apache Kafka® clusters, as well as create, modify, delete, run, and stop them.
- View Apache Kafka® cluster logs.
- View information about quotas of Managed Service for Apache Kafka®.
- View information about resource operations for Managed Service for Apache Kafka®.
This role includes the permissions of the managed-kafka.viewer
role.
To create Apache Kafka® clusters, you also need the vpc.user
role.
managed-kafka.admin
The managed-kafka.admin
role allows you to manage Apache Kafka® clusters and view their logs, as well as get information about quotas and service resource operations.
Users with this role can:
- Manage access to Apache Kafka® clusters.
- View information about Apache Kafka® clusters, as well as create, modify, delete, run, and stop them.
- View Apache Kafka® cluster logs.
- View information about quotas of Managed Service for Apache Kafka®.
- View information about resource operations for Managed Service for Apache Kafka®.
This role includes the permissions of the managed-kafka.editor
role.
To create Apache Kafka® clusters, you also need the vpc.user
role.
mdb.auditor
The mdb.auditor
role grants the minimum permissions required to view information about managed database clusters (without access to data or runtime logs).
Users with this role can view information about managed database clusters, quotas, and folders.
It includes the permissions of the managed-elasticsearch.auditor
, managed-opensearch.auditor
, managed-kafka.auditor
, managed-mysql.auditor
, managed-sqlserver.auditor
, managed-postgresql.auditor
, managed-greenplum.auditor
, managed-clickhouse.auditor
, managed-redis.auditor
, and managed-mongodb.auditor
roles.
mdb.viewer
The mdb.viewer
role grants read access to managed database clusters and cluster runtime logs.
Users with this role can read from databases, inspect the logs of managed database clusters, and view information about clusters, quotas, and folders.
It includes the permissions of the mdb.auditor
, managed-elasticsearch.viewer
, managed-opensearch.viewer
, managed-kafka.viewer
, managed-mysql.viewer
, managed-sqlserver.viewer
, managed-postgresql.viewer
, managed-greenplum.viewer
, managed-clickhouse.viewer
, managed-redis.viewer
, managed-mongodb.viewer
, and dataproc.viewer
roles.
mdb.admin
The mdb.admin
role grants full access to managed database clusters.
Users with this role can create, edit, delete, run, and stop managed database clusters, manage cluster access, read and write to databases, and view information about clusters, runtime logs, quotas, and folders.
It includes the permissions of the mdb.viewer
, vpc.user
, managed-elasticsearch.admin
, managed-opensearch.admin
, managed-kafka.admin
, managed-mysql.admin
, managed-sqlserver.admin
, managed-postgresql.admin
, managed-greenplum.admin
, managed-clickhouse.admin
, managed-redis.admin
, managed-mongodb.admin
, and dataproc.admin
roles.
vpc.publicAdmin
The vpc.publicAdmin
role grants access to managing public IP addresses and external connectivity.
Users with this role can create and delete public IP addresses and manage external connectivity.
It includes the permissions of the vpc.viewer
role.
The scope of this role can be a cloud or folder. Important: If a network and subnet are in different folders, the vpc.publicAdmin
role is checked for the folder where the network is located.
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.
Roles required
To use the service, you need the managed-kafka.editor
role or higher for the folder where a cluster is created. The managed-kafka.viewer
role only enables you to view the cluster list.
You can always assign a role with more permissions. For instance, you can assign managed-kafka.admin
instead of managed-kafka.editor
.