diff --git a/modules/get-started/pages/whats-new-cloud.adoc b/modules/get-started/pages/whats-new-cloud.adoc
index f94dfbd2c..2f6683352 100644
--- a/modules/get-started/pages/whats-new-cloud.adoc
+++ b/modules/get-started/pages/whats-new-cloud.adoc
@@ -46,6 +46,10 @@ The Redpanda Terraform provider (v2.1.0+) now supports enabling and managing Red
 
 The Redpanda Terraform provider (v2.0.0+) now supports managing cluster secrets with the new `redpanda_secret` resource. The secret value is a write-only attribute, so Terraform never stores it in your state file, and scopes control which features can use the secret, such as Redpanda Connect pipelines. See xref:manage:terraform-provider.adoc#manage-cluster-secrets[Manage cluster secrets].
 
+=== Terraform provider: Shadow link management
+
+The Redpanda Terraform provider (v2.0.0+) now supports managing shadow links for disaster recovery on BYOC and Dedicated clusters with the new `redpanda_shadow_link` resource. Define the link between source and shadow clusters, client connection settings, and topic, consumer group, ACL, and Schema Registry synchronization options in code, with the source cluster password stored as a cluster secret rather than in your state file. See the link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/shadow_link[redpanda_shadow_link reference^] and xref:manage:disaster-recovery/shadowing/setup.adoc[Configure Shadowing].
+
 === Centralized egress for BYOC on GCP: beta
 
 You can route all GCP BYOC cluster egress through your own GCP hub VPC and NAT VM instead of a per-cluster Cloud NAT, so outbound traffic exits through your centralized inspection point. This is useful for regulated environments that require a single, predictable public IP for outbound allowlisting or that prohibit per-cluster Cloud NAT. Centralized egress is in a glossterm:beta[] release and is enabled per organization. Contact your account team for access. See xref:networking:byoc/gcp/nat-free-egress.adoc[Configure Centralized Egress with GCP VPC Peering].
diff --git a/modules/manage/pages/terraform-provider.adoc b/modules/manage/pages/terraform-provider.adoc
index e5ac4a685..825ade58f 100644
--- a/modules/manage/pages/terraform-provider.adoc
+++ b/modules/manage/pages/terraform-provider.adoc
@@ -22,6 +22,7 @@ With the Redpanda Terraform provider, you can manage:
 * link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/secret[Secrets^]
 * link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/serverless_cluster[Serverless clusters^]
 * link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/serverless_private_link[Serverless private links^]
+* link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/shadow_link[Shadow links^]
 * link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/topic[Topics^]
 * link:https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs/resources/user[Users^]