[
https://issues.apache.org/jira/browse/FLINK-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709154#comment-15709154
]
ASF GitHub Bot commented on FLINK-4611:
---------------------------------------
GitHub user tony810430 opened a pull request:
https://github.com/apache/flink/pull/2914
[FLINK-4611] Make "AUTO" credential provider as default for Kinesis C…
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tony810430/flink FLINK-4611
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2914.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 #2914
----
commit be8b22fc3d8dd1c5aa97800c988fe4492b94993e
Author: 魏偉哲 <tonywei@tonyweis-macbook-pro.local>
Date: 2016-11-30T10:17:24Z
[FLINK-4611] Make "AUTO" credential provider as default for Kinesis
Connector
----
> Make "AUTO" credential provider as default for Kinesis Connector
> ----------------------------------------------------------------
>
> Key: FLINK-4611
> URL: https://issues.apache.org/jira/browse/FLINK-4611
> Project: Flink
> Issue Type: Improvement
> Components: Kinesis Connector
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Wei-Che Wei
> Fix For: 1.2.0
>
>
> Right now, the Kinesis Consumer / Producer by default directly expects the
> access key id and secret access key to be given in the config properties.
> This isn't a good practice for accessing AWS services, and usually Kinesis
> users would most likely be running their Flink application in AWS instances
> that have embedded credentials that can be access via the default credential
> provider chain. Therefore, it makes sense to change the default
> {{AWS_CREDENTIALS_PROVIDER}} to {{AUTO}} instead of {{BASIC}}.
> To avoid breaking user code, we only use directly supplied AWS credentials if
> both access key and secret key is given through {{AWS_ACCESS_KEY}} and
> {{AWS_SECRET_KEY}}. Otherwise, the default credential provider chain is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
