Skip to content

Commit 82fae39

Browse files
authored
Merge pull request #4359 from ClickHouse/kk/rpe-subnets-clarification
2 parents 7844f13 + 7bad07e commit 82fae39

File tree

1 file changed

+14
-6
lines changed

1 file changed

+14
-6
lines changed

docs/integrations/data-ingestion/clickpipes/aws-privatelink.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,19 @@ To set up PrivateLink with VPC resource:
5454
2. Create a resource configuration
5555
3. Create a resource share
5656

57-
#### 1. Create a Resource-Gateway {#create-resource-gateway}
57+
#### 1. Create a resource gateway {#create-resource-gateway}
5858

59-
Resource-Gateway is the point that receives traffic for specified resources in your VPC.
59+
Resource gateway is the point that receives traffic for specified resources in your VPC.
6060

61-
You can create a Resource-Gateway from the [AWS console](https://docs.aws.amazon.com/vpc/latest/privatelink/create-resource-gateway.html) or with the following command:
61+
:::note
62+
Your resource gateway attached subnets are recommended to have sufficient IP addresses available.
63+
It's recommended to have at least `/26` subnet mask for each subnet.
64+
65+
For each VPC endpoint (each Reverse Private Endpoint), AWS requires a consecutive block of 16 IP addresses per subnet. (`/28` subnet mask)
66+
If this requirement is not met, Reverse Private Endpoint will transition to a failed state.
67+
:::
68+
69+
You can create a resource gateway from the [AWS console](https://docs.aws.amazon.com/vpc/latest/privatelink/create-resource-gateway.html) or with the following command:
6270

6371
```bash
6472
aws vpc-lattice create-resource-gateway \
@@ -68,9 +76,9 @@ aws vpc-lattice create-resource-gateway \
6876
--name <RESOURCE_GATEWAY_NAME>
6977
```
7078

71-
The output will contain a Resource-Gateway id, which you will need for the next step.
79+
The output will contain a resource gateway id, which you will need for the next step.
7280

73-
Before you can proceed, you'll need to wait for the Resource-Gateway to enter into an `Active` state. You can check the state by running the following command:
81+
Before you can proceed, you'll need to wait for the resource gateway to enter into an `Active` state. You can check the state by running the following command:
7482

7583
```bash
7684
aws vpc-lattice get-resource-gateway \
@@ -79,7 +87,7 @@ aws vpc-lattice get-resource-gateway \
7987

8088
#### 2. Create a VPC Resource-Configuration {#create-resource-configuration}
8189

82-
Resource-Configuration is associated with Resource-Gateway to make your resource accessible.
90+
Resource-Configuration is associated with resource gateway to make your resource accessible.
8391

8492
You can create a Resource-Configuration from the [AWS console](https://docs.aws.amazon.com/vpc/latest/privatelink/create-resource-configuration.html) or with the following command:
8593

0 commit comments

Comments
 (0)