You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Moritz Mack (Jira)" <ji...@apache.org> on 2022/03/03 13:53:00 UTC
[jira] [Commented] (BEAM-13956) Serialize/deserialize StsClient when serializing/deserializing StsAssumeRoleCredentialsProvider
[ https://issues.apache.org/jira/browse/BEAM-13956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500765#comment-17500765 ]
Moritz Mack commented on BEAM-13956:
------------------------------------
[~i_maravic] Sorry, took a bit to get things merged, I was off for a couple of days...
> Serialize/deserialize StsClient when serializing/deserializing StsAssumeRoleCredentialsProvider
> -----------------------------------------------------------------------------------------------
>
> Key: BEAM-13956
> URL: https://issues.apache.org/jira/browse/BEAM-13956
> Project: Beam
> Issue Type: Improvement
> Components: io-java-aws
> Reporter: Igor Maravić
> Priority: P3
> Labels: aws, aws-sdk-v2
>
> To use _StsAssumeRoleCredentialsProvider_ from the environment that doesn't have access to AWS defaults credentials one needs to provide configured _StsClient_ to {_}StsAssumeRoleCredentialsProvider{_}.
> If we don't serialize and consequently deserialize _StsClient_ that was provided to _StsAssumeRoleCredentialsProvider,_ we're not going to be able to use _StsAssumeRoleCredentialsProvider_ from the Beam pipeline.
> The goal of this ticket is to introduce this functionality.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)