Merge pull request #4351 from ClickHouse/kk/clarify-cluster-publicly-accessible

fix(docs): Clarify restrictions on resource configuration for publicly accessible clusters for ClickPipes

Author: jkaflik

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

@@ -103,6 +103,14 @@ aws vpc-lattice create-resource-configuration \
     --resource-configuration-definition 'arnResource={arn=arn:aws:rds:us-east-1:123456789012:cluster:my-rds-cluster}'
 ```
 
+:::note
+You can't create a resource configuration for a publicly accessible cluster.
+If your cluster is publicly accessible, you must modify the cluster
+to make it private before creating the resource configuration 
+or use [IP allow list](/integrations/clickpipes#list-of-static-ips) instead. 
+For more information, see the [AWS documentation](https://docs.aws.amazon.com/vpc/latest/privatelink/resource-configuration.html#resource-definition).
+:::
+
 The output will contain a Resource-Configuration ARN, which you will need for the next step. It will also contain a Resource-Configuration ID, which you will need to set up a ClickPipe connection with VPC resource.
 
 #### 3. Create a Resource-Share {#create-resource-share}
@@ -113,7 +121,7 @@ You can put the Resource-Configuration into the Resource-Share through [AWS cons
 
 ```bash
 aws ram create-resource-share \
-    --principals arn:aws:iam::072088201116:root \
+    --principals 072088201116 \
     --resource-arns <RESOURCE_CONFIGURATION_ARN> \
     --name <RESOURCE_SHARE_NAME>
 ```