You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. Workspace Level (workspace level users/groups, workspace objects like clusters)
18
18
19
-
The 2 levels of resources use different providers configs and have different authentication method, username/password is the only method for account level provider authentication.
19
+
The 2 levels of resources use different providers configs and have different authentication method, client ID/client secret is the only method for account level provider authentication.
20
20
21
21
For workspace level provider you can create `n` databricks providers for `n` existing workspaces, each provider to be authenticate via PAT token.
22
22
23
-
We propose 2-stage process to get onboarded to UC. Starting at the point where you only have `account owner`, and this identity will also be the first `account admin`. Account admins can add/remove other `account admin`.
23
+
We propose 2-stage process to get onboarded to UC. Starting at the point where you only have `account owner`, and this identity will also be the first `account admin`. Account admins can add/remove other account admins, including service principals.
24
24
25
25
We recommend using `account admin` identities to deploy unity catalog related resources.
> Step 2: Run `terraform init` and `terraform apply` to deploy the resources. This will deploy both AWS resources that Unity Catalog requires and Databricks Account Level resources.
29
+
> Step 2: Run `terraform init` and `terraform apply` to deploy the resources. This will deploy both AWS resources that Unity Catalog requires and Databricks Account Level resources.
Copy file name to clipboardExpand all lines: examples/aws-exfiltration-protection/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,8 @@ This template provides an example deployment of AWS Databricks E2 workspace with
20
20
2. Add a `variables.tf` with the same content in [variables.tf](variables.tf)
21
21
3. Add a `terraform.tfvars` file and provide values to each defined variable
22
22
4. Configure the following environment variables:
23
-
*TF_VAR_databricks_account_username, set to the value of your Databricks account-level admin username.
24
-
*TF_VAR_databricks_account_password, set to the value of the password for your Databricks account-level admin user.
23
+
*TF_VAR_databricks_account_client_id, set to the value of application ID of your Databricks account-level service principal with admin permission.
24
+
*TF_VAR_databricks_account_client_secret, set to the value of the client secret for your Databricks account-level service principal.
25
25
* TF_VAR_databricks_account_id, set to the value of the ID of your Databricks account. You can find this value in the corner of your Databricks account console.
26
26
5. (Optional) Configure your [remote backend](https://developer.hashicorp.com/terraform/language/settings/backends/s3)
27
27
6. Run `terraform init` to initialize terraform and get provider ready.
0 commit comments