Ben,
Thanks so much for this advice! Unfortunately I can’t seem to get Dremio to connect to the wasabi host (s3.wasabisys.com).
Here are the parameters I used:
The exceptions sometimes show Dremio attempting to connect to sts.amazonaws.com, and other times don’t list host names - they never show traffic to s3.wasabisys.com
at com.dremio.plugins.s3.store.STSCredentialProviderV1.getCredentials(STSCredentialProviderV1.java:71)
at org.apache.hadoop.fs.s3a.AWSCredentialProviderList.getCredentials(AWSCredentialProviderList.java:137)
… 47 common frames omitted
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to sts.amazonaws.com:80 [sts.amazonaws.com/54.239.29.25] failed: Connection refused (Connection refused)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:159)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
i.e.:
cat /var/log/dremio/server.log | grep -C3 wasabisys.com
returns nothing
I installed Wasabi’s CA cert and restarted Dremio, but this had no effect.
I can ping s3.wasabisys.com
ping s3.wasabisys.com
PING s3.wasabisys.com (38.27.106.12) 56(84) bytes of data.
64 bytes from 38.27.106.12 (38.27.106.12): icmp_seq=1 ttl=54 time=1.78 ms
and using the IP address makes no difference.
It sure looks to me like Dremio is connecting to AWS instead of Wasabi.
Any suggestions on how to get it connect to Wasabi instead?
Thanks,
Eric