From 381dd525945c61cd34d9eac73f93c2b50859a2c2 Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Thu, 16 Jul 2026 20:35:34 -0400 Subject: [PATCH 1/2] DOC-2021: Point cross-region PrivateLink readers to Terraform support The supported_regions Terraform field has existed since provider v1.8.0 but the platform page only named the Cloud UI and Cloud API as configuration methods. Add the cross-link and note the multi-AZ requirement on the Terraform example. Co-Authored-By: Claude Fable 5 --- modules/manage/pages/terraform-provider.adoc | 2 +- modules/networking/pages/aws-privatelink.adoc | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/modules/manage/pages/terraform-provider.adoc b/modules/manage/pages/terraform-provider.adoc index 65e530ffb..0a6620566 100644 --- a/modules/manage/pages/terraform-provider.adoc +++ b/modules/manage/pages/terraform-provider.adoc @@ -630,7 +630,7 @@ resource "redpanda_cluster" "test" { enabled = true connect_console = true allowed_principals = ["arn:aws:iam::123456789024:root"] - supported_regions = ["us-east-1", "us-west-2"] # Optional: Enable cross-region PrivateLink + supported_regions = ["us-east-1", "us-west-2"] # Optional: Enable cross-region PrivateLink (requires a multi-AZ cluster) } tags = { "environment" = "dev" diff --git a/modules/networking/pages/aws-privatelink.adoc b/modules/networking/pages/aws-privatelink.adoc index 19f46cf00..4aa39a6a0 100644 --- a/modules/networking/pages/aws-privatelink.adoc +++ b/modules/networking/pages/aws-privatelink.adoc @@ -267,6 +267,8 @@ The `supported_regions` field accepts a list of AWS region identifiers where you With this configuration, clients in VPCs located in `us-east-1`, `us-west-2`, and `eu-west-1` can create PrivateLink endpoints that connect to your Redpanda cluster, regardless of which region the cluster is deployed in. +If you manage your clusters with the Redpanda Terraform provider, set the same `supported_regions` field in the `aws_private_link` block of the `redpanda_cluster` resource. See xref:manage:terraform-provider.adoc#create-a-dedicated-cluster[Create a Dedicated cluster] for an example, and the https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/cluster[redpanda_cluster resource documentation^] for the full schema. + === Create a cross-region VPC endpoint When creating a VPC endpoint in a different region than your Redpanda cluster, use the same process as <>, but specify both the client VPC's region and the service region where your Redpanda cluster is deployed. From fb836fd376075c0c97f5beaeb0cd786e0a56b5c4 Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Mon, 20 Jul 2026 19:37:47 -0400 Subject: [PATCH 2/2] Drop Terraform pointer superseded by cloud-docs#635 After merging main, the Configure cross-region PrivateLink section carried two Terraform pointers: #635's intro sentence (targeting the provider page's purpose-built cross-region section) and this PR's paragraph (targeting the generic Dedicated-cluster example). Keep #635's. Also for the record: supported_regions shipped in provider v1.7.0, not v1.8.0 as this PR's original commit message said (verified in #635 by SME review against the tag). Co-Authored-By: Claude Fable 5 --- modules/networking/pages/aws-privatelink.adoc | 2 -- 1 file changed, 2 deletions(-) diff --git a/modules/networking/pages/aws-privatelink.adoc b/modules/networking/pages/aws-privatelink.adoc index 2b5af64cd..42d8ec0ec 100644 --- a/modules/networking/pages/aws-privatelink.adoc +++ b/modules/networking/pages/aws-privatelink.adoc @@ -267,8 +267,6 @@ The `supported_regions` field accepts a list of AWS region identifiers where you With this configuration, clients in VPCs located in `us-east-1`, `us-west-2`, and `eu-west-1` can create PrivateLink endpoints that connect to your Redpanda cluster, regardless of which region the cluster is deployed in. -If you manage your clusters with the Redpanda Terraform provider, set the same `supported_regions` field in the `aws_private_link` block of the `redpanda_cluster` resource. See xref:manage:terraform-provider.adoc#create-a-dedicated-cluster[Create a Dedicated cluster] for an example, and the https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/cluster[redpanda_cluster resource documentation^] for the full schema. - === Create a cross-region VPC endpoint When creating a VPC endpoint in a different region than your Redpanda cluster, use the same process as <>, but specify both the client VPC's region and the service region where your Redpanda cluster is deployed.