Skip to main content
This section provides information on the key mechanisms for controlling access to StreamNative Cloud resources, including the StreamNative Cloud resource hierarchy, role-based access control (RBAC), and access control lists (ACLs).

​
Resource hierarchy

StreamNative Cloud organizes resources in a hierarchical structure to manage access and permissions effectively. The top-level resource is the organization, which can contain multiple instances. Each instance can include various resources, such as Pulsar/Kafka Clusters, Workspaces, and more. This hierarchy allows you to manage access and permissions at different levels, ensuring that you can control access to resources based on your organizational structure and security policies. See Resources on StreamNative Cloud for more details.

​
Role-based access control (RBAC)

Role-based access control (RBAC) allows you to manage access to StreamNative Cloud resources by assigning predefined roles to users, service accounts, and other entities. Each role is associated with a set of permissions that determine the actions that can be performed on specific resources. By using RBAC, you can control access to resources based on roles and responsibilities, ensuring that only authorized users can perform certain actions. See Role-Based Access Control for more details.

​
Access control lists (ACLs)

Access control lists (ACLs) provide fine-grained access control to Pulsar resources in StreamNative Cloud. ACLs allow you to control which users or service accounts can perform specific actions on Pulsar resources, such as tenants, namespaces, topics, and more. By using ACLs, you can ensure that only authorized users can access and manage Pulsar resources, enhancing security and preventing unauthorized access. ACLs can be used in conjunction with RBAC to provide a comprehensive access control mechanism. See Authorization and ACLs for more details.