flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tzu-Li (Gordon) Tai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8417) Support STSAssumeRoleSessionCredentialsProvider in FlinkKinesisConsumer
Date Fri, 12 Jan 2018 16:37:01 GMT

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

Tzu-Li (Gordon) Tai commented on FLINK-8417:
--------------------------------------------

Fro the Javadocs, it mentions that the {{STSAssumeRoleSessionCredentialsProvider}} spawns
a background thread that automatically refreshes the credentials. I assume then that is handled
out-of-the-box by the AWS API?

> Support STSAssumeRoleSessionCredentialsProvider in FlinkKinesisConsumer
> -----------------------------------------------------------------------
>
>                 Key: FLINK-8417
>                 URL: https://issues.apache.org/jira/browse/FLINK-8417
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kinesis Connector
>            Reporter: Tzu-Li (Gordon) Tai
>             Fix For: 1.5.0
>
>
> As discussed in ML: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Kinesis-Connectors-With-Temporary-Credentials-td17734.html.
> Users need the functionality to access cross-account AWS Kinesis streams, using AWS Temporary
Credentials [1].
> We should add support for {{AWSConfigConstants.CredentialsProvider.STSAssumeRole}}, which
internally would use the {{STSAssumeRoleSessionCredentialsProvider}} [2] in {{AWSUtil#getCredentialsProvider(Properties)}}.
> [1] https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html
> [2] https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/STSAssumeRoleSessionCredentialsProvider.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message