You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using a AWS S3 Endpoint Interface that runs inside a VPCE is a way to access S3 buckets without going through the public internet. This is useful for security and performance reasons.
The endpoint provides a special URL scheme: https://bucket.vpce-xxxxxxxxxxxxxxxxx-xxxxxx.s3.us-east-1.vpce.amazonaws.com and problem is that Clickhouse fails to use the private endpoint, but works with public ones, like https://s3.us-east-1.amazonaws.com.
Using url_schemes_mappers won't work because the URL scheme uses bucket.vpce-xxxxxxxxxxxxxxxxx-xxxxxx as the bucket identifier and clickhouse expects a bucket name without .:
Use case
Using a AWS S3 Endpoint Interface that runs inside a VPCE is a way to access S3 buckets without going through the public internet. This is useful for security and performance reasons.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html
The endpoint provides a special URL scheme:
https://bucket.vpce-xxxxxxxxxxxxxxxxx-xxxxxx.s3.us-east-1.vpce.amazonaws.com
and problem is that Clickhouse fails to use the private endpoint, but works with public ones, likehttps://s3.us-east-1.amazonaws.com
.Using url_schemes_mappers won't work because the URL scheme uses
bucket.vpce-xxxxxxxxxxxxxxxxx-xxxxxx
as the bucket identifier and clickhouse expects a bucket name without.
:ClickHouse/src/IO/S3/URI.cpp
Line 38 in ddaef8d
Describe the solution you'd like
Support a new URL scheme for S3 VPCE endpoints.
Describe alternatives you've considered
Using S3Proxy and Global Proxy settings
#51749
Additional context
Stack trace:
The text was updated successfully, but these errors were encountered: