VK Cloud logo

Access managementBeta

To differentiate rights for invited members of a project or service accounts, Cloud Kafka uses a unified identity and access management service — IAM. Access can be managed centrally from the VK Cloud personal dashboard.

The list of actions available to a project member in the Cloud Kafka service is determined by:

The Cloud Kafka service has no specialized roles.

Only project members with the Project Owner, Superadministrator, and User Administrator (IAM) roles can assign roles and permissions. When granting roles and permissions, follow the principle of least privilege: a user should have only the rights without which their tasks cannot be performed.

Role model example

The basic roles Project Owner, Superadministrator, and Project Administrator get full access to all Cloud Kafka operations; configuring individual permissions is not needed.

To differentiate access, the basic role User Administrator (IAM) or Observer can be used with additional permissions. By default, access to Cloud Kafka for these basic roles is limited:

  • User Administrator (IAM): no access.
  • Observer: can only view some information about previously created Cloud Kafka service instances.

You can grant any permissions, creating a role model that suits you.

Full access

All actions are allowed, including creating and deleting Cloud Kafka service instances. This access level can be used by a project member with broad expertise and a high degree of responsibility. Creating new service instances can increase infrastructure costs, and deletion is an irreversible operation that can disrupt the operation of an application using your Cloud Kafka service instance.

Infrastructure administration

Has almost all permissions except creating and deleting Cloud Kafka service instances. Can be used by a project member acting as an infrastructure operator or DevOps engineer to manage already created service instances. It also implies an impact on the cost of services, but only through scaling existing service instances.

Service usage

Has no access to service instance management and can only view information about them, except for audit data. Also allows creating, deleting, and viewing mirror connections for data replication between Kafka clusters. Can be used by project members working with data, for example, developers or data engineers.

Security audit

Cannot change the parameters of a Cloud Kafka service instance and has no access to the service graphical interface in the personal dashboard. Used exclusively for audit: examining logs and event history, as well as viewing the list of users. Typically suitable for security department employees.

Was this article helpful?