[
https://issues.apache.org/jira/browse/BEAM-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433647#comment-17433647
]
Moritz Mack commented on BEAM-8958:
-----------------------------------
Current IO modules with AWS client providers using access key/secret rather
than a configurable credentials provider:
* aws (sdk v1)
** dynamodb
** sns
* kinesis (sdk v1)
** though AWSModule for serialization not available
* aws (sdk v2)
** kinesis
[~aromanenko] I suppose this ticket meant the v2 module? Does it make sense to
expand the scope of this to tackle the other cases? The only "problematic"
candidate seems to be kinesis v1
> Use default credentials provider with BasicKinesisProvider
> ----------------------------------------------------------
>
> Key: BEAM-8958
> URL: https://issues.apache.org/jira/browse/BEAM-8958
> Project: Beam
> Issue Type: Improvement
> Components: io-java-kinesis
> Reporter: Alexey Romanenko
> Assignee: Moritz Mack
> Priority: P3
>
> For the moment, only {{AWSStaticCredentialsProvider}} with
> {{BasicAWSCredentials}} is used as default credentials provider for
> KinesisIO. It would be helpful and more secure to provide a way of using
> other credentials providers as well without implementing own
> \{{BasicAWSCredentials}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
