You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/05/25 16:22:08 UTC

[jira] [Updated] (FLINK-8416) Kinesis consumer doc examples should demonstrate preferred default credentials provider

     [ https://issues.apache.org/jira/browse/FLINK-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-8416:
---------------------------------
    Fix Version/s:     (was: 1.5.0)
                   1.5.1

> Kinesis consumer doc examples should demonstrate preferred default credentials provider
> ---------------------------------------------------------------------------------------
>
>                 Key: FLINK-8416
>                 URL: https://issues.apache.org/jira/browse/FLINK-8416
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Kinesis Connector
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Major
>             Fix For: 1.4.3, 1.3.4, 1.5.1
>
>
> The Kinesis consumer docs [here](https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/connectors/kinesis.html#kinesis-consumer) demonstrate providing credentials by explicitly supplying the AWS Access ID and Key.
> The always preferred approach for AWS, unless running locally, is to automatically fetch the shipped credentials from the AWS environment.
> That is actually the default behaviour of the Kinesis consumer, so the docs should demonstrate that more clearly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)