mj006648 commented on code in PR #4451: URL: https://github.com/apache/polaris/pull/4451#discussion_r3302814694
########## site/content/in-dev/unreleased/configuration/configuring-polaris-for-production/configuring-aws-s3-cloud-storage-specific.md: ########## @@ -0,0 +1,258 @@ +--- +# +# 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 S3 Storage +linkTitle: Configuring S3 Storage +type: docs +weight: 610 +--- + +This page covers configuring AWS S3, and S3-compatible object stores (MinIO, Apache Ozone S3 +gateway, Ceph RGW, and similar), as the storage backend for a Polaris catalog. On AWS S3, all read +and write operations are performed using credential vending: Polaris assumes a customer IAM role +via STS and returns scoped, short-lived credentials to the client. The IAM role, its trust policy, +and the bucket itself must be set up before the catalog is created. + +This page is limited to native Polaris authentication. External identity providers are also +supported but are not yet covered here; the configuration patterns below remain otherwise the same. + +## IAM role and trust policy Review Comment: Thanks @flyrain. Took a shot at this in 0837f0a4a — added an overview section naming the three identities and a "Polaris service identity" section covering IRSA / EC2 / static creds plus the sts:AssumeRole policy. Also renamed the old section to "Catalog access role and trust policy" so the labels line up. Quick check: I read "creating a new catalog" as the IAM role that gets bound to the catalog at creation time. If you meant the admin permissions to call the catalogs API, let me know and I'll handle it separately. -- 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]
