BYOVPC prereq and bucket name clarification

Author: kbatuigas

modules/manage/pages/iceberg/about-iceberg-topics.adoc

@@ -45,7 +45,7 @@ When you enable the Iceberg integration for a Redpanda topic, Redpanda brokers s
 To enable Iceberg for Redpanda topics, you must have the following:
 
 ifdef::env-cloud[]
-* A running xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster on Redpanda version 25.1 or later. The Iceberg integration is supported only for BYOC, and the cluster properties to configure Iceberg are available with v25.1.
+* A running xref:get-started:cluster-types/byoc/index.adoc[BYOC] or BYOVPC cluster on Redpanda version 25.1 or later. The Iceberg integration is supported only for BYOC and BYOVPC, and the cluster properties to configure Iceberg are available with v25.1.
 * rpk: See xref:get-started:rpk-install.adoc[].
 * Familiarity with the Redpanda Cloud API. You must link:/api/doc/cloud-controlplane/authentication[authenticate] to the Cloud API and use the Control Plane API to update your cluster configuration.
 endif::[]
@@ -189,26 +189,9 @@ ifdef::env-cloud[]
 
 === Access Iceberg data
 
-To query the Iceberg table, you need access to the object storage bucket or container where the Iceberg data is stored. For BYOC clusters, the bucket name and table location are as follows:
+To query the Iceberg table, you need access to the object storage bucket or container where the Iceberg data is stored.
 
-|===
-| Cloud provider | Bucket or container name | Iceberg table location
-
-| AWS
-| `redpanda-cloud-storage-<cluster-id>`
-.3+a| `redpanda-iceberg-catalog/redpanda/<topic-name>`
-
-| Azure
-a| `<cluster-id>`
-
-The Redpanda cluster ID is also used as the container name (ID) and the storage account ID.
-
-
-| GCP
-| `redpanda-cloud-storage-<cluster-id>`
-
-
-|===
+include::manage:partial$iceberg-access-table.adoc[]
 
 For Azure clusters, you must add the public IP addresses or ranges from the REST catalog service, or other clients requiring access to the Iceberg data, to your cluster's allow list. Alternatively, add subnet IDs to the allow list if the requests originate from the same Azure region.
 

modules/manage/pages/iceberg/iceberg-topics-databricks-unity.adoc

@@ -73,7 +73,7 @@ Follow the steps in the https://docs.databricks.com/aws/en/connect/unity-catalog
 The external location stores the Unity Catalog-managed Iceberg metadata, and the Iceberg data written by Redpanda. You must use the same bucket configured for glossterm:Tiered Storage[] for your Redpanda cluster.
 
 ifdef::env-cloud[]
-For BYOC clusters, the bucket name is `redpanda-cloud-storage-<cluster-id>`, where `<cluster-id>` is the ID of your Redpanda cluster.
+For BYOC clusters, the bucket name is `redpanda-cloud-storage-<cluster-id>`, where `<cluster-id>` is the ID of your Redpanda cluster. For BYOVPC clusters, the bucket name is the name you chose when you created the Tiered Storage bucket as a customer-managed resource.
 endif::[]
 
 Follow the steps in the https://docs.databricks.com/aws/en/connect/unity-catalog/cloud-storage/external-locations[Databricks documentation] to *manually* create an external location. You can create the external location in the Catalog Explorer or with SQL. You must create the external location manually because the location needs to be associated with the existing Tiered Storage bucket URL, `s3://<bucket-name>`.