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:ย 

"account users" system group has the Account admin role. Can it be removed, and how do we get a per-

xavi-albert
New Contributor

We manage Databricks on AWS with Terraform (databricks provider 1.x), using one Unity Catalog metastore shared by several workspaces. Each customer gets its own workspace, an ISOLATED catalog, an ISOLATED storage credential, and an ISOLATED external location, all bound only to that customer's workspace.

Goal: each customer's catalog IAM role should trust only its own storage credential's external ID, so that a new storage credential pointed at another customer's role is refused by AWS (confused deputy protection beyond workspace bindings).

Our Terraform creates the storage credential first, reads aws_iam_role[0].external_id from it, and puts that value in the IAM role's trust policy as sts:ExternalId. This follows the order in the Unity Catalog on AWS guide.

What we see: the external_id returned for the new credential is our Databricks account ID, not a per-credential UUID.

The KB article "AWS S3 storage credential validation failure due to external ID" explains this: credentials created by an account admin get the account ID, and credentials created by anyone else get a random ID. Terraform runs as a service principal that is an account admin, so we planned to create storage credentials with a second service principal that is not an account admin.

The blocker: in the account console, a new service principal shows Account admin as "Role inherited from groups can't be changed here." Its only parent group is the system group account users. The SCIM API confirms that account users has roles: ["account_admin"], so every user and service principal in the account inherits account admin.

We searched system.access.audit for any event assigning account_admin to that group (service_name = 'accounts' with account_admin in request_params) and found nothing. The grant either predates our audit history or isn't recorded that way.

Questions:

  1. Is Account admin on account users something Databricks sets on some accounts, or does it only appear when an admin assigns it?
  2. Can an account admin remove the Account admin role from account users? The docs say system groups can't have their entitlements modified, but don't say whether that applies to account-level roles.
  3. If it can be removed, is the safe order to assign Account admin directly to the users who still need it, and then remove it from the group? Is there anything else to check first, such as the account owner?
  4. If it can't be removed, is there any supported way to create a storage credential that gets a per-credential external ID while every identity in the account is an account admin?

Thanks!

2 REPLIES 2

saurabh18cs
Honored Contributor III

Hi @xavi-albert it is possible that users group at account level has been granted account admin entitlement switched on. This looks like a manual intervention. Otherwise grant this account admin entitlement to few chosen one users.

below is example from workspace users group but account level users group will have different entitlements and one will be account admin

saurabh18cs_0-1793783159848.png

 

 

xavi-albert
New Contributor

Hi @saurabh18cs , thank you for the reply! I can confirm that Account admin was turned on for the Databricks managed account users group by someone and we since turned it off. I can now proceed with my build.