by
Bas1
• New Contributor III
- 13508 Views
- 16 replies
- 20 kudos
In Azure Databricks the DBFS storage account is open to all networks. Changing that to use a private endpoint or minimizing access to selected networks is not allowed.Is there any way to add network security to this storage account? Alternatively, is...
- 13508 Views
- 16 replies
- 20 kudos
Latest Reply
How can we secure the storage account in the managed resource group which holds the DBFS with restricted network access, since access from all networks is blocked by our Azure storage account policy?
15 More Replies
- 4027 Views
- 3 replies
- 0 kudos
Hi, Thoroughly investigating the best security practices for accessing the Databricks WEB UI. I have doubts about the difference between protecting the WEB UI with (1) IP Access list (https://learn.microsoft.com/en-us/azure/databricks/security/networ...
- 4027 Views
- 3 replies
- 0 kudos
Latest Reply
"In short, would it be the same to configure only the IP of the private endpoint in the IP access list vs disable public access?"The access list doesn't apply to private IPs, only to public IP (internet). Relevant part from the docs:"If you use Priva...
2 More Replies
- 4688 Views
- 3 replies
- 5 kudos
Hi there,I'm helping a client of mine set up an Azure Databricks environment. The workspace is set up for private access only, and we are using Azure Firewall and Azure Private Link.We have the network environment successfully configured to the point...
- 4688 Views
- 3 replies
- 5 kudos
Latest Reply
Hi @Nick Barretta I'm sorry you could not find a solution to your problem in the answers provided.Our community strives to provide helpful and accurate information, but sometimes an immediate solution may only be available for some issues.I suggest ...
2 More Replies
- 5172 Views
- 2 replies
- 8 kudos
I have created a workspace in AWS with private link. When we launch a cluster we get the following error: "Security Daemon Registration Exception: Failed to set up the spark container due to an error when registering the container to security daemon"...
- 5172 Views
- 2 replies
- 8 kudos
Latest Reply
Thanks @Sivaprasad C S It's already working. The problem was that the AWS STS private link was wrongly associated with the correct subnet.
1 More Replies
