Starburst Access Control overview#
Starburst access control is the access control system of Starburst Control Plane. It’s a role-based access control (RBAC) system that also supports attribute-based access control (ABAC) on your data. You grant privileges and policies to roles. Policies control access, filter rows, and mask columns based on attributes of the data, such as its tags or names. You define these rules once in the Control Plane, and each Starburst Enterprise platform (SEP) cluster that connects to it enforces them.
Starburst access control works only in the Control Plane, and it controls data access only in governed catalogs. Delegated catalogs keep their existing access control.
You can also manage Starburst access control with the Control Plane API.
Note
Starburst access control is a public preview feature. Contact Starburst Support with questions or feedback.
How it works#
With Starburst access control, you grant privileges to roles, not to users, and users get access by assuming a role that is available to them. A privilege allows or denies an action, such as reading a table, on a catalog, schema, table, or column.
You can extend RBAC with ABAC by granting policies to roles. A policy applies to the data in its scope that matches a matching expression, such as data with a specific tag or with a name that matches a pattern. A policy can allow or deny privileges on that data, filter its rows, or mask its columns. Policies apply only to data privileges, not to account privileges.
To decide whether a user can perform an action, Starburst access control adds
together the privileges of the user’s active role set,
from direct grants and from policies. The active role set is the user’s current
role plus all roles that are granted to it, directly or through other roles. A
DENY from any source overrides an allow.
Each catalog in the Control Plane uses one of two access control modes.
Governed catalogs use Starburst access control. Your roles, privileges, and policies decide who can access the catalog and its data.
Delegated catalogs keep their existing access control, such as built-in access control on the cluster. Starburst access control rules don’t apply to their data, but Starburst access control still controls some actions in every catalog, such as roles and storage locations. For more information, see Compare with built-in access control.
Starburst access control also controls access to features of the Control Plane. You grant privileges for actions such as creating catalogs and viewing the query history of all users. For a list of these privileges, see Privileges for Control Plane features.
When a user runs a query, the cluster evaluates the user’s access using the
rules in the Control Plane. It uses the user’s current role, which is the
one role that the user acts under at a time, and its active role set. By
default, the current role is the user’s default role. In the Control Plane UI,
a user can switch to another role that they can assume. Clients that send
queries to the Control Plane can set the current role with the
X-Trino-Role header, such as X-Trino-Role: system=ROLE{analyst}. For more
information, see
Client request headers.
Compare with built-in access control#
Built-in access control manages access separately on each SEP cluster. Starburst access control manages access for governed catalogs from the Control Plane, so you define your rules once for all of your clusters, and you can also use tags and policies. For more information, see Compare with built-in access control.
Requirements#
To use Starburst access control, you need the following:
A Control Plane installation configured for Starburst access control, as described in Configuration
SEP clusters that run in managed mode, which you set with the
deployment.mode=MANAGEDanddeployment.manager.uripropertiesAt least one administrator user or group, which you set with the
starburst.access-control.authorized-usersorstarburst.access-control.authorized-groupsproperty
Features that require Starburst access control#
The following Control Plane features work only when Starburst access control is
enabled. If you set one of these properties without
control-plane.enabled=true, the Control Plane doesn’t start:
Feature |
Property |
|---|---|
AI models |
|
Background work |
|
Context Studio |
|
Data products |
|
LakeOps, including live tables and Kafka ingest |
|
LDAP and SCIM user provisioning |
|
Model Context Protocol (MCP) endpoint |
|
Resource groups |
|
Enabling Starburst access control also turns on catalog management and the access control pages in the Control Plane UI. Other Control Plane features, such as the query editor, query routing, and the Starburst Metastore, work with or without Starburst access control. When Starburst access control is enabled, Starburst access control privileges control who can use them.
Limitations#
Starburst access control has the following limitations:
Starburst access control doesn’t work with a Control Plane that only routes queries.
ALLandNONEroles aren’t supported. Users act under one role at a time.Policy matching expressions don’t support user attributes.
Governed catalogs don’t currently support credential pass-through, user impersonation, Apache Ranger, or AWS Lake Formation. User impersonation isn’t supported because Starburst access control grants privileges and ownership to roles, not to users.
Governed catalogs must use system security, such as
hive.security=system. The Control Plane sets it by default for Hive, Iceberg, and Delta Lake catalogs. To use another security setting, make the catalog delegated.To query a delegated catalog in the Control Plane query editor, users must hold a role from the delegated system, such as a built-in access control role. All of the user’s roles from that system apply. In other clients, users can select one built-in access control role with the
$biac-roleextra credential. For more information, see Select a built-in access control role.The Control Plane doesn’t record access to data. Its audit log records changes, not queries. Use cluster-level audit logging for access events.
Starburst access control doesn’t govern session properties. Users can set any system or catalog session property.
Service accounts aren’t supported.
See also#
For more information about Starburst access control, see the following pages: