dennishuo opened a new issue, #2436: URL: https://github.com/apache/polaris/issues/2436
### Is your feature request related to a problem? Please describe. https://github.com/apache/polaris/pull/1913 added support for customizing S3 and STS endpoints, which is very useful for non-AWS S3-compatible support. However, since Polaris ultimately serves two different personas of users: 1. Polaris service owners 2. Catalog users The usage of custom endpoints requires multi-party consent from both personas. At a minimum this means we need a FeatureConfiguration that allows Service Owners to decide whether to allow their "Catalog users" to set custom s3/sts endpoints. That would be sufficient control for simple well-contained Polaris deployments to enable the feature without impacting more complex multi-tenant deployments. For more complex architectures involving partial or no-trust between the service owner and catalog users, we probably also want to introduce some kind of allowlisting mechanism so that the custom endpoints still need to follow a well-defined structure. ### Describe the solution you'd like _No response_ ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- 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]
