How do I figure out what public IP ranges my Databricks workspace clusters are coming from?

McDonald, Matthew 186 Reputation points
2024-05-08T22:13:53.72+00:00

Edit: I am rewriting this to clarify the ask.


Relatively new to Databricks. I am trying to understand how outbound traffic from clusters is determined. It seems to differ if SCC is enabled vs when it's not.

With no SCC:

VMs start up with a dedicated public IP. Traffic is sourced from it.

With SCC:

VMs start with no public IP. Outbound traffic appears to come from ranges identified at https://video2.skills-academy.com/en-us/azure/databricks/resources/supported-regions#outbound

I have an existing workspace that cannot have SCC enabled at this time, but I need to whitelist the IPs that these VMs would be coming from. I just can't seem to find any information as to what configures these dedicated public IPs, and from what ranges.

TIA

Azure Databricks
Azure Databricks
An Apache Spark-based analytics platform optimized for Azure.
2,174 questions
{count} votes

Accepted answer
  1. PRADEEPCHEEKATLA-MSFT 89,376 Reputation points Microsoft Employee
    2024-05-20T05:42:40.1833333+00:00

    @McDonald, Matthew - Thanks for the question and using MS Q&A platform.

    Based on the information you provided, it seems that your Databricks workspace clusters are not using the documented outbound NAT ranges. This could be because SCC is disabled and the clusters are using their own dedicated public IP addresses.

    In this case, you can try the following steps to determine the public IP addresses/ranges that your clusters are using:

    1. Check the Azure portal for the public IP addresses associated with the virtual machines (VMs) that are running your Databricks clusters. You can find this information by navigating to the VMs in the Azure portal and looking at the "Public IP address" field.

    Once you have the public IP addresses, you can use a tool like IP2Location to determine the IP ranges that they belong to. This will give you an idea of the IP ranges that your clusters are communicating on.

    If the IP ranges you find are not the same as the documented outbound NAT ranges, you can try whitelisting the specific IP addresses instead of the entire range. Alternatively, you can try enabling SCC to use the documented ranges.

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.