flyrain commented on code in PR #3066:
URL: https://github.com/apache/polaris/pull/3066#discussion_r2548126018


##########
site/content/in-dev/unreleased/configuring-polaris-for-production/configuring-gcs-cloud-storage-specific.md:
##########
@@ -0,0 +1,37 @@
+---
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+title: Configuring GCS Cloud Storage
+linkTitle: Configuring GCS Cloud Storage
+type: docs
+weight: 600
+---
+
+This page provides guidance for Configuring GCS Cloud Storage provider for use 
with Polaris. 
+It covers credential vending, IAM roles, ACL requirements, and best practices 
to ensure secure and reliable integration.
+
+#### GCS
+
+When using credential vending for Google Cloud Storage (GCS) with Apache 
Iceberg on
+Polaris, ensure that both IAM roles and HNS ACLs (if HNS is enabled) are 
properly configured. Even with the correct IAM
+role (e.g., `roles/storage.objectAdmin`), access to paths such as 
`gs://<bucket>/idsp_ns/sample_table4/` may fail with
+403 errors if HNS ACLs are missing for scoped tokens. The original access 
token may work, but scoped (vended) tokens
+require HNS ACLs on the base path or relevant subpath. Polaris does not 
require HNS to be enabled for basic operation,

Review Comment:
   What are basic operations? Can we clarify that? My impression is that we 
cannot disable credential vending when a catalog based on GCS. In that case, 
HNS seems mandatory.  



##########
site/content/in-dev/unreleased/configuring-polaris-for-production/configuring-gcs-cloud-storage-specific.md:
##########
@@ -0,0 +1,37 @@
+---
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+title: Configuring GCS Cloud Storage
+linkTitle: Configuring GCS Cloud Storage
+type: docs
+weight: 600
+---
+
+This page provides guidance for Configuring GCS Cloud Storage provider for use 
with Polaris. 
+It covers credential vending, IAM roles, ACL requirements, and best practices 
to ensure secure and reliable integration.
+
+#### GCS
+
+When using credential vending for Google Cloud Storage (GCS) with Apache 
Iceberg on
+Polaris, ensure that both IAM roles and HNS ACLs (if HNS is enabled) are 
properly configured. Even with the correct IAM

Review Comment:
   Does HNS refer to Hierarchical namespace described here, 
https://docs.cloud.google.com/storage/docs/hns-overview? We might add the full 
name and links so that reader arent' confused the by the acronym. 



##########
site/content/in-dev/unreleased/configuring-polaris-for-production/configuring-gcs-cloud-storage-specific.md:
##########
@@ -0,0 +1,37 @@
+---
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+title: Configuring GCS Cloud Storage
+linkTitle: Configuring GCS Cloud Storage
+type: docs
+weight: 600
+---
+
+This page provides guidance for Configuring GCS Cloud Storage provider for use 
with Polaris. 
+It covers credential vending, IAM roles, ACL requirements, and best practices 
to ensure secure and reliable integration.
+
+#### GCS

Review Comment:
   We don't need this title as this page is dedicated for GCS config



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to