Skip to content

Commit 85fc469

Browse files
committed
Edit BYOC Page
1 parent 1a070d9 commit 85fc469

File tree

1 file changed

+1
-24
lines changed

1 file changed

+1
-24
lines changed

docs/cloud/reference/byoc.md

Lines changed: 1 addition & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -163,30 +163,7 @@ In the peering AWS account,
163163
<br />
164164

165165
#### Step 6 Edit Security Group to allow Peered VPC access {#step-6-edit-security-group-to-allow-peered-vpc-access}
166-
In ClickHouse BYOC account,
167-
1. In the ClickHouse BYOC account, navigate to EC2 and locate the Private Load Balancer named like infra-xx-xxx-ingress-private.
168-
169-
<br />
170-
171-
<Image img={byoc_plb} size="lg" alt="BYOC Private Load Balancer" border />
172-
173-
<br />
174-
175-
2. Under the Security tab on the Details page, find the associated Security Group, which follows a naming pattern like `k8s-istioing-istioing-xxxxxxxxx`.
176-
177-
<br />
178-
179-
<Image img={byoc_security} size="lg" alt="BYOC Private Load Balancer Security Group" border />
180-
181-
<br />
182-
183-
3. Edit the Inbound Rules of this Security Group and add the Peered VPC CIDR range (or specify the required CIDR range as needed).
184-
185-
<br />
186-
187-
<Image img={byoc_inbound} size="lg" alt="BYOC Security Group Inbound Rule" border />
188-
189-
<br />
166+
In the ClickHouse BYOC account, you'll need to update the Security Group settings to allow traffic from your peered VPC. Please contact ClickHouse Support to request the addition of inbound rules that include the CIDR ranges of your peered VPC.
190167

191168
---
192169
The ClickHouse service should now be accessible from the peered VPC.

0 commit comments

Comments
 (0)