GitHub user pduveau opened a pull request: https://github.com/apache/flink/pull/5411
[FLINK-8556] [Kinesis Connector] Add proxy feature to the connector ## The purpose of the change The connector can not be configured to use a proxy to access Kinesis endpoint. This feature is required if running on EC2 instances which can access internet only through a proxy. VPC Kinesis endpoints are currently available in few AWS' regions. ## Change log The configuration is extended with new parameters for all supported proxy of the AWS Client Configuration. Can be configured as Anonymous or with any combination of authentication's methods BASIC, DIGEST, SPNEGO, KERBEROS and NTML. ## Verifying this change No test added to check those optionnal paramaters. The check is done at runtime by validating the configuration. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? yes - If yes, how is the feature documented? JavaDocs You can merge this pull request into a Git repository by running: $ git pull https://github.com/pduveau/flink Kinesis_add_proxy_parameters Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/5411.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5411 ---- commit 89dcc7b34f0eb1ba3d412919b0ece89bc822f056 Author: Philippe Duveau <philippe.duveau@...> Date: 2018-02-04T11:25:15Z Adds proxy feature to the connector to access Kinesis endpoint. ---- ---