- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2026 02:54 AM
Hi @kohei-matsumura,
Yes.. if you want to find changes to account-console roles on a service principal (for example, who has roles/servicePrincipal.manager or roles/servicePrincipal.user), then service_name = 'accountsAccessControl' and action_name = 'updateRuleSet' is the right audit event family to search. The account-console permissions flow for service principals is handled by the Accounts Access Control API, and grant/revoke is done by updating the rule set for that service principal resource.
But those two predicates alone are too broad if your goal is a specific service principal. They will return all rule-set updates made through the Account Access Control API, not just service-principal-manager changes.
What else that search can include:
- updates to the account rule set: accounts/<ACCOUNT_ID>/ruleSets/default
- updates to a group rule set: accounts/<ACCOUNT_ID>/groups/<GROUP_ID>/ruleSets/default
- updates to a service principal rule set: accounts/<ACCOUNT_ID>/servicePrincipals/<SP_ID>/ruleSets/default
- updates to a tag policy rule set: accounts/<ACCOUNT_ID>/tagPolicies/<TAG_POLICY_ID>/ruleSets/default
So for your use case, the better filter is:
- service_name = 'accountsAccessControl'
- action_name = 'updateRuleSet'
- request_params['account_id'] = '<account-id>'
- get_json_object(request_params['name'], '$.name') = 'accounts/<account-id>/servicePrincipals/<sp-id>/ruleSets/default'
That narrows the results to updates to that service principal’s rule set specifically. Also note... updateRuleSet is a full replacement of the rule set, not a single "grant one user" delta event. One audit record can therefore represent multiple additions/removals/changes at once, depending on the final contents of request_params['rule_set'].
If you want to specifically inspect who can manage the SP, look inside the rule set for roles/servicePrincipal.manager. If you also care about who can use it, look for roles/servicePrincipal.user as well.
Some links if you find them useful..
https://docs.databricks.com/aws/en/dev-tools/cli/reference/account-access-control-commands
https://docs.databricks.com/aws/en/security/auth/access-control/service-principal-acl
If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***