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
Copy file name to clipboardExpand all lines: docs/integrations/data-ingestion/clickpipes/aws-privatelink.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,11 +54,19 @@ To set up PrivateLink with VPC resource:
54
54
2. Create a resource configuration
55
55
3. Create a resource share
56
56
57
-
#### 1. Create a Resource-Gateway {#create-resource-gateway}
57
+
#### 1. Create a resource gateway {#create-resource-gateway}
58
58
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.
60
60
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:
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.
72
80
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:
#### 2. Create a VPC Resource-Configuration {#create-resource-configuration}
81
89
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.
83
91
84
92
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:
0 commit comments