You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Danny Cranmer (Jira)" <ji...@apache.org> on 2022/10/31 14:59:00 UTC

[jira] [Commented] (FLINK-29496) Add Configuration for STS endpoint when using ASSUME_ROLE credential provider

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

Danny Cranmer commented on FLINK-29496:
---------------------------------------

Merged commit [{{79712e1}}|https://github.com/apache/flink/commit/79712e16adc13a9ccac016178fd3dcb551afbab3] into master

> Add Configuration for STS endpoint when using ASSUME_ROLE credential provider
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-29496
>                 URL: https://issues.apache.org/jira/browse/FLINK-29496
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kinesis
>    Affects Versions: 1.16.0, 1.15.2
>            Reporter: Aleksandr Pilipenko
>            Assignee: Aleksandr Pilipenko
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.17.0
>
>
> When using Kinesis connector with credentials provider configured as ASSUME_ROLE in the job running in VPC without internet connection, credentials provider logic tries to access global STS endpoint, {{{}sts.amazonaws.com{}}}. However, only regional endpoints for STS are available in that case.
> Connector need support for configuring STS endpoint to allow such use-case.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)