From ce802ff52e23f479e229490a997b7951e6eff7ab Mon Sep 17 00:00:00 2001 From: Maxim Leonovich Date: Fri, 1 Aug 2025 15:05:45 -0700 Subject: [PATCH] docs: fix in the AWS private link doc --- .../product/deployment/cloud/byoc/aws/privatelink.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/pages/product/deployment/cloud/byoc/aws/privatelink.mdx b/docs/pages/product/deployment/cloud/byoc/aws/privatelink.mdx index 61c2ceaf3e477..ee43f7742446b 100644 --- a/docs/pages/product/deployment/cloud/byoc/aws/privatelink.mdx +++ b/docs/pages/product/deployment/cloud/byoc/aws/privatelink.mdx @@ -66,6 +66,15 @@ To enable proper hostname resolution, create a private Route 53 hosted zone: - **Domain name**: `.cubecloudapp.dev` - **Type**: Private hosted zone - **VPCs**: Associate with your target VPC(s) + + + +The `` placeholder in the domain name should be replaced with the exact region identifier provided by Cube Cloud support. This is **not** the standard AWS region name (like `us-east-1`), but rather a Cube Cloud-specific identifier that uniquely identifies your BYOC infrastructure provisioning. + +For example, if Cube Cloud provides you with a region identifier like `aws-us-east-1-t-12345-prod`, you would use that exact string in place of ``. + + + 4. Create the following DNS records in the zone: | Record Name | Type | Value | @@ -74,6 +83,8 @@ To enable proper hostname resolution, create a private Route 53 hosted zone: | `*.sql..cubecloudapp.dev` | A | Alias to SQL VPC endpoint | | `sql..cubecloudapp.dev` | A | Alias to SQL VPC endpoint | + **Note**: Each BYOC infrastructure provisioning will have a different region identifier. If you provision additional regions in the future, each will require its own private zone with the corresponding region-specific identifier. + ### Step 4: Verify connectivity To test the connection from within your VPC, obtain the test connection commands from the Cube Cloud UI: