[
https://issues.apache.org/jira/browse/ASTERIXDB-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392344#comment-17392344
]
Ingo Müller commented on ASTERIXDB-2940:
----------------------------------------
Actually, setting the environment variable
{{JAVA_OPTS=-Dhttp.proxyHost=proxy.ethz.ch -Dhttp.proxyPort=3128
-Dhttps.proxyHost=proxy.ethz.ch -Dhttps.proxyPort=3128}} seems to be enough in
my case, at least for the sample cluster (via {{start-sample-cluster.sh}}).
Maybe this is obvious if you are familiar with Java but I didn't think of it
immediately...
> Make HTTP proxy of S3 client configurable
> -----------------------------------------
>
> Key: ASTERIXDB-2940
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2940
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: EXT - External data
> Affects Versions: 0.9.8
> Reporter: Ingo Müller
> Priority: Major
>
> It would be great if the S3 client used for external data set would work
> behind corporate proxies. The ClientConfiguration class of the AWS SDK has a
> number of attributes that should make that work easily (see
> [setProxyDomain|https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/ClientConfiguration.html#setProxyDomain-java.lang.String-]
> and similar), however, these must be set by the application (I suppose that
> this would happen in buildAwsS3Client).
> Any other method to enable AsterixDB to access S3 through a proxy should be
> fine too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
