[
https://issues.apache.org/jira/browse/FLINK-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15462090#comment-15462090
]
ASF GitHub Bot commented on FLINK-4559:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/2470
Thanks for the review @greghogan.
I think it makes sense to let `AUTO` be the default, as the usual use case
for most AWS users is to auto-detect the credentials delivered to instances by
AWS's metadata service. Changing this should not break user code either. Would
you like to open the ticket for that?
> Kinesis Producer not setting credentials provider properly when
> AWS_CREDENTIALS_PROVIDER is "AUTO"
> --------------------------------------------------------------------------------------------------
>
> Key: FLINK-4559
> URL: https://issues.apache.org/jira/browse/FLINK-4559
> Project: Flink
> Issue Type: Bug
> Components: Kinesis Connector
> Affects Versions: 1.1.0, 1.1.1, 1.1.2
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Minor
> Fix For: 1.1.3
>
>
> If the {{AWS_CREDENTIAL_PROVIDER}} option is set to {{AUTO}},
> {{AWSUtils.getCredentialsProvider}} will return {{null}}, so
> {{setCredentialsProvider}} should not be explicitly called on the internally
> built {{KinesisProducerConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
