Hi folks,
This is regarding the addition of KMS support for AWS S3 in Polaris. Several approaches were proposed in the PR <https://github.com/apache/polaris/pull/1424>, and based on our last community sync, we aligned on the following: - Using an IAM policy with *Resource: '*'* at the catalog level (Approach #4) - Using table-level keys as per the Iceberg spec (Approach #3) The current PR <https://github.com/apache/polaris/pull/1424> implements Approach #4 at the catalog level. I’d like to confirm whether it’s okay to split the implementation and submit Approach #3 as a separate PR. PR - https://github.com/apache/polaris/pull/1424
