You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge pull request #14 from dnks0/feature/dbx-proxy
* added validation to avoid conflicts where the proxy health port is also used as a listener port
* streamlined bootstrap deployments to also include a security group on the NLB
* ingress is bypassed on the NLB SG due to limitations
* ingress to the NLB is controlled via the endpoint-service
* included NLB security groups into module outputs
Before going to production, please review the following [limitations & trade-offs](terraform/README.md#limitations--tradeoffs-of-the-current-implementation).
89
+
Before going to production, please review the following [limitations & trade-offs](terraform/README.md#limitations--tradeoffs-of-the-current-implementation).
Copy file name to clipboardExpand all lines: terraform/README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -283,3 +283,9 @@ This module is intentionally minimal right now. The following limitations are im
283
283
- Databricks enforces limits around NCCs, private endpoints, and private endpoint rules (including limits on the number of domain names per rule).
284
284
- Treat these as **external constraints** that influence how you model `dbx_proxy_listener`.
285
285
- Reference: [Configure private connectivity to resources in your VPC](https://docs.databricks.com/aws/en/security/network/serverless-network-security/pl-to-internal-network).
286
+
287
+
-**PrivateLink NLB SG ingress enforcement**
288
+
- Currently, if bootstrapped, the NLB gets created with a dedicated Security Group attached, which would allow to control ingress to the NLB, enforced with `enforce_security_group_inbound_rules_on_private_link_traffic = on`.
289
+
- The above setting would also allow to see individual client-IPs as source in network packets (which would be favorable in general)
290
+
- However, we are not able to lock-down the inbound rules on the NLB Security Group due to missing information like Security Group ID or VPC endpoint ID of the consumer side (Databricks Serverless).
291
+
- Therefore, we are using `enforce_security_group_inbound_rules_on_private_link_traffic = on`, which bypasses the Security Group inbound rules, and solely rely on the endpoint service `allowed_principals` and manual acceptance to control inbound traffic to the NLB.
[forlinvar.dbx_proxy_listener: { port = l.port, description ="Databricks to NLB to dbx-proxy listener ${l.name}" }],
13
-
contains([forlinvar.dbx_proxy_listener:l.port], var.dbx_proxy_health_port) ? [] :[{ port = var.dbx_proxy_health_port, description ="Databricks to NLB to dbx-proxy health check" }],
12
+
[{ port = var.dbx_proxy_health_port, description ="Databricks to NLB to dbx-proxy health check" }],
0 commit comments