[
https://issues.apache.org/jira/browse/BEAM-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433743#comment-17433743
]
Moritz Mack commented on BEAM-8958:
-----------------------------------
i've previously ignored the S3Options / AwsOptions as it rather looked like the
outlier. But I agree, it would dramatically cut down config boilerplate in case
there's multiple AWS IO connectors present. I'll read a bit more about
pipeline options and ping you then.
{quote}Well, it would be great to add this for two versions of KinesisIO, I
guess it should be pretty similar, iirc.
{quote}
Kinesis (for SDK v1) is currently a separate module. So that would require
copying the code required for serialization of the CredentialsProvider there as
well. Apart from that not a big deal ...
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
