Skip to content

Commit

Permalink
Update website/docs/docs/cloud/secure/vcs-privatelink.md
Browse files Browse the repository at this point in the history
Co-authored-by: Leona B. Campbell <[email protected]>
  • Loading branch information
matthewshaver and runleonarun authored Dec 1, 2023
1 parent 540442b commit 1e4376f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/docs/cloud/secure/vcs-privatelink.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This document will cover at a high level the resources necessary to implement th

### Solution resources

Creating an Interface VPC PrivateLink connection requires creating multiple AWS resources in the account containing the self-hosted VCS instance. You are responsible for provisioning and maintaining the resources deployed within your AWS account(s) and private network. Once provisioned, connection information and permissions are shared with dbt Labs to complete the connection, allowing for direct VPC to VPC private connectivity.
Creating an Interface VPC PrivateLink connection requires creating multiple AWS resources in your AWS account(s) and private network containing the self-hosted VCS instance. You are responsible for provisioning and maintaining these resources. Once provisioned, connection information and permissions are shared with dbt Labs to complete the connection, allowing for direct VPC to VPC private connectivity.

Note: This approach is distinct from and does not require you to implement VPC peering between your AWS account(s) and dbt Cloud.

Expand Down

0 comments on commit 1e4376f

Please sign in to comment.