Are Repos HIPAA compliant, or is there a plan and timeline to support this? Customer is getting a warning when trying to enable the Repos feature in a HIPAA deployment on Azure Databricks.
There is a plan to support this. For timeline, please reach out to your Databricks account team.
Unfortunately this is not possible. The default user workspace name will be the user's email address.
I am working on a disaster recovery plan for my environment which includes Databricks. Where do I start with my planning? What all do I need to consider when building a DR plan?
Depending on your RPO/RTOs there are different recovery solution strategies that could be considered (active/passive, active/active) for Databricks deployments. A detailed explanation of these approaches are mentioned here
I would like it if I could make it so that the credentials of the user who initiates a job are used as the credentials for the job run. Is this possible?
Is this in Azure? If so, it is not supported currently. https://docs.microsoft.com/en-us/azure/databricks/security/credential-passthrough/adls-passthrough
Yes. We support this.Please see https://docs.databricks.com/administration-guide/workspace/storage.html#modify-the-storage-location-for-notebook-results and https://docs.databricks.com/administration-guide/workspace/storage.html#configure-the-storage...
All Databricks workspaces are deployed with this setting as of Q1 of 2021.
Yes. Users can have access to multiple workspaces. Workspaces are units of collaboration.
Databricks only charges for compute time while machines are being used. If a machine is on "IDLE" then Databricks does not charge you for those machines. The cloud providers will charge you for the machines that are running regardless if they are IDL...
Yes, you need an Azure Databricks account on the Premium plan to enable Databricks SQL
Yes. It is not self-service. We can "merge" accounts on AWS, such that you can manage all your Databricks workspaces from a single place at https://accounts.cloud.databricks.com/loginPlease contact your Databricks Representative.
Customer has to delete it.
The DEK is cached in memory for several read/write operations and evicted from memory at a regular interval such that new requests require another request to your cloud service’s key management system. If you delete or revoke your key, reading or wri...
Doc link - https://docs.databricks.com/security/keys/customer-managed-keys-notebook-aws.htmlHow long the DEK key is cached in-memory?
These permissions are one of the list described here in Step 6.chttps://docs.databricks.com/administration-guide/account-api/iam-role.htmlIt is required because we use tags to identify the owners, and other minimum information, of clusters on AWS. It...
The recipient’s client authenticates to the sharing server (via a bearer token or other method) and asks to query a specific table. The client can also provide filters on the data (e.g. “country=US”) as a hint to read just a subset of the data.The se...
