Skip to content

Commit d719306

Browse files
committed
Move grant access addition to new PR
1 parent cfa83dc commit d719306

File tree

1 file changed

+1
-18
lines changed

1 file changed

+1
-18
lines changed

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

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -27,24 +27,7 @@ endif::[]
2727
ifdef::env-cloud[]
2828
Redpanda generates an Iceberg table with the same name as the topic. Depending on the processing engine and your Iceberg catalog implementation, you may also need to define the table (for example using `CREATE TABLE`) to point the data lakehouse to its location in the catalog.
2929

30-
For BYOC clusters, the bucket name and table location are as follows:
31-
32-
|===
33-
| Cloud provider | Bucket or container name | Iceberg table location
34-
35-
| AWS
36-
| `redpanda-cloud-storage-<cluster-id>`
37-
.3+a| `redpanda-iceberg-catalog/redpanda/<topic-name>`
38-
39-
| Azure
40-
a| `<cluster-id>`
41-
42-
The Redpanda cluster ID is also used as the container name (ID) and the storage account ID.
43-
44-
| GCP
45-
| `redpanda-cloud-storage-<cluster-id>`
46-
47-
|===
30+
include::manage:partial$iceberg-access-table.adoc[]
4831

4932
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.
5033

0 commit comments

Comments
 (0)