cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

"Break Glass" access for QA and PROD environments

dbx_687_3__1b3Q
New Contributor III

We're a small team with three environments (development, qa, and production), each in a separate workspace. Our deployments are automated through CI/CD practices with manual approval gates to deploy to the qa and production environments.

We'd like to implement access akin to "break glass" accounts for our qa and production environments. This would require extra effort from the user in order to make manual changes - outside the CI/CD process - in those environments. 

This concept would be similar to Privileged Identity Management (PIM) in Microsoft Azure but implemented in Databricks. A user's default permissions would be read-only in the qa and production environments but the user could gain elevated permissions by activating their assigned PIM roles.

How can we implement this? Should we create a "daily driver" account that users use for most activities and second "admin" account for the break glass access? Is there a better approach?

0 REPLIES 0

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group