[
https://issues.apache.org/jira/browse/BEAM-13956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495616#comment-17495616
]
Moritz Mack commented on BEAM-13956:
------------------------------------
[~i_maravic] another small PR to prepare ClientConfiguration for serialization
in pipeline options. [https://github.com/apache/beam/pull/16894]
Are you planning to work on this ticket? Then I'll assign it to you.
With the PR above it should be quite manageable to serialize & restore the Sts
client:
# Get SdkClientConfiguration of client using reflection, read needed options
from configuration (AwsClientOption.CREDENTIALS_PROVIDER,
AwsClientOption.AWS_REGION) and store in ClientConfiguration for serialization.
# Deserialize ClientConfiguration and use ClientBuilderFactory to create the
client.
{code:java}
ClientBuilderFactory.defaultFactory(StsClient.builder(), configuration,
null).build(){code}
> Serialize/deserialize used 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)
