+1, I think this is a good idea. If there is a similar concept for the other storage types, could we consider adding that too?
* https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints --EM On Tue, Jun 24, 2025 at 9:23 PM Dmitri Bourlatchkov <di...@apache.org> wrote: > Hi All, > > I propose to add an `endpoint` optional parameter to AwsStorageConfigInfo > in PR [1913]. > > The main idea is to support non-AWS S3 implementations for [1530]. > > Existing classes related to supporting S3 Polaris are coded to the AWS SDK, > which supports setting STS endpoints. Therefore, it seems natural to allow > users to optionally define a specific endpoint for their catalogs. > > This change is backward-compatible with existing clients and deployed > catalogs. > > When an endpoint is defined it will be used for both STS and S3 requests > inside Polaris and will be used to populate the "s3.endpoint" properties in > REST Catalog clients. > > Thoughts? > > [1530] https://github.com/apache/polaris/issues/1530 > [1913] https://github.com/apache/polaris/pull/1913 > > Thanks, > Dmitri. >
