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

[ricelso]

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.

[Sai_Ponugoti]

Hey @ricelso ,
Sorry to hear about the issue you are facing.
At the moment, firewall enablement for serverless compute is only supported in these regions.
Could you let me know which region your workspace is in?

This feature is currently supported only on workspaces with the Premium plan or higher, and it requires you to be enrolled in the Public Preview, as this has not yet reached GA.

Could you also confirm which Databricks edition you’re using, and whether your workspace is enrolled in the Public Preview?
In addition, have you tried creating a new NCC to check whether the stable IPs appear there?

You can find more details about the requirements on our website.