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


##########
site/content/in-dev/unreleased/configuring-polaris-for-production/configuring-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 Cloud Storage

Review Comment:
   sounds good!!



##########
site/content/in-dev/unreleased/configuring-polaris-for-production/_index.md:
##########
@@ -234,3 +234,7 @@ profile (for example, `%prod`).
 
 The [Polaris Evolution](../evolution) page discusses backward compatibility and
 upgrade concerns.
+
+### Configuring Polaris for Cloud Storages
+
+For guidance on configuring cloud storage providers (such as Google Cloud 
Storage, Amazon S3, and Azure Blob Storage) for use with Polaris—including 
credential vending, IAM roles, ACL requirements, and best practices—see 
[Configuring Cloud Storage](./configuring-cloud-storage-specific/).

Review Comment:
   cool!!



-- 
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