Learn how to use Role Based Access Control to govern engines
Use Role Based Access Control (RBAC) to granularly control which users within an account can create new engines, use, operate, monitor and modify existing engines. Accordingly, Firebolt provides CREATE, USAGE, OPERATE, MONITOR and MODIFY permissions to control these actions. You can use RBAC to control whether a user has permissions to perform these actions for specific engines or for all engines in a given account. Note that permissions for CREATE ENGINE can only be granted at the account level.
Follow the below steps to control what permissions a user has for a given engine or for any engine within an account:
Example 1: We want to provide a user kate with permissions to create and operate engines
User, organization, and role names that contain non-alphanumeric characters other than underscores (_
) must be enclosed in double-quotes. Double-quotes also preserve uppercase characters when needed. For more information about the full set of naming rules, see the object identifiers guide.
Example 2: We want to provide a user kate with permissions to only use and operate engines
Example 3: We want to provide a user kate with permissions to use, operate and monitor engine metrics
Example 4: We want to provide a user kate with permissions to create and modify engines
Engines permissions reference guide can be found here
Learn how to use Role Based Access Control to govern engines
Use Role Based Access Control (RBAC) to granularly control which users within an account can create new engines, use, operate, monitor and modify existing engines. Accordingly, Firebolt provides CREATE, USAGE, OPERATE, MONITOR and MODIFY permissions to control these actions. You can use RBAC to control whether a user has permissions to perform these actions for specific engines or for all engines in a given account. Note that permissions for CREATE ENGINE can only be granted at the account level.
Follow the below steps to control what permissions a user has for a given engine or for any engine within an account:
Example 1: We want to provide a user kate with permissions to create and operate engines
User, organization, and role names that contain non-alphanumeric characters other than underscores (_
) must be enclosed in double-quotes. Double-quotes also preserve uppercase characters when needed. For more information about the full set of naming rules, see the object identifiers guide.
Example 2: We want to provide a user kate with permissions to only use and operate engines
Example 3: We want to provide a user kate with permissions to use, operate and monitor engine metrics
Example 4: We want to provide a user kate with permissions to create and modify engines
Engines permissions reference guide can be found here