[ 
https://issues.apache.org/jira/browse/BEAM-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433714#comment-17433714
 ] 

Alexey Romanenko commented on BEAM-8958:
----------------------------------------

Well, it would be great to add this for two versions of KinesisIO, I guess it 
should be pretty similar, iirc. 

Perhaps, we need to re-think the design of this since there are two basic ways 
of authentication for AWS services now in Beam - with {{AwsModule}} (Jackson 
module) for S3 and with own implementation of {{AwsClientsProvider}} for every 
AWS IO connector that Beam supports. Imo, it would be great to have a one 
unified way of authentication for all of them (for SDK v1 and v2 separately, of 
course). In this case, we will need to deprecate an old API for sure.

Btw, SDK v1 connectors are supposed to be deprecated and removed in the feature 
but we need to make sure that SDK v2  connectors support everything that v1 
modules support.



> 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: 10m
>  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)

Reply via email to