cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

AWS-Databricks' workspace attached to a NCC doesn't generate Egress Stable IPs

ricelso
Visitor

I am facing an issue when configuring a Databricks workspace on AWS with a Network Connectivity Configuration (NCC).
Even after attaching the NCC, the workspace does not generate Egress Stable IPs as expected.

In the workspace configuration tab, under Network Connectivity Configuration, it shows:

Egress Stable IPs: .

Egress via PrivateLink: 0 VPC endpoints

So, no stable IPs are being assigned.

 

Impact:

I cannot obtain the Egress Stable IPs required to configure firewall rules and allow controlled communication with external systems.

This blocks integration with systems that rely on IP whitelisting.

Steps already taken:

Created and attached the NCC to the workspace.

Validated the cross-account role permissions.

Checked the documentation, which indicates that Egress Stable IPs should be listed.

Expected behavior:
When a workspace is attached to an NCC, Databricks should generate and display the Egress Stable IPs.

0 REPLIES 0

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now