Skip to content

Commit 37104e2

Browse files
authored
Merge pull request #3471 from ClickHouse/multi-regional-aws-pl
Cross-Region Connectivity for AWS PrivateLink
2 parents e982808 + 8f2c77d commit 37104e2

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

docs/cloud/security/aws-privatelink.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,9 @@ import aws_private_link_ped_nsname from '@site/static/images/cloud/security/aws-
2222
You can use [AWS PrivateLink](https://aws.amazon.com/privatelink/) to provide connectivity between VPCs, AWS services, your on-premises systems, and ClickHouse Cloud without having your traffic go across the internet. This document describes how to connect to ClickHouse Cloud using AWS PrivateLink. To disable access to your ClickHouse Cloud services from addresses other than AWS PrivateLink addresses use ClickHouse Cloud [IP Access Lists](/cloud/security/setting-ip-filters).
2323

2424
:::note
25-
ClickHouse Cloud currently does not support [cross-region PrivateLink](https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/). However, you can [connect to PrivateLink using VPC peering](https://aws.amazon.com/about-aws/whats-new/2019/03/aws-privatelink-now-supports-access-over-vpc-peering/). For more information and configuration guidance, please refer to AWS documentation.
25+
ClickHouse Cloud currently supports [cross-region PrivateLink](https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/) in beta.
2626
:::
2727

28-
2928
Please complete the following steps to enable AWS Private Link:
3029
1. Obtain Endpoint Service name.
3130
1. Create a service endpoint.
@@ -107,6 +106,10 @@ Select **Other endpoint services** and use the `endpointServiceId` you got from
107106

108107
<img src={aws_private_link_endpoint_settings} alt="AWS PrivateLink Endpoint Settings" />
109108

109+
If you want to establish a cross-regional connection via PrivateLink, enable the "Cross region endpoint" checkbox and specify the service region. The service region is where the ClickHouse instance is running.
110+
111+
If you get a "Service name could not be verified." error, please contact Customer Support to request adding new regions to the supported regions list.
112+
110113
Next, select your VPC and subnets:
111114

112115
<img src={aws_private_link_select_vpc} alt="Select VPC and subnets" />
@@ -156,6 +159,7 @@ resource "aws_vpc_endpoint" "this" {
156159
]
157160
subnet_ids = [var.subnet_id1,var.subnet_id2,var.subnet_id3]
158161
private_dns_enabled = false
162+
service_region = "(Optional) If specified, the VPC endpoint will connect to the service in the provided region. Define it for multi-regional PrivateLink connections."
159163
}
160164
```
161165

-27.7 KB
Loading

0 commit comments

Comments
 (0)