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/03 15:39:00 UTC

[jira] [Updated] (FLINK-29496) Unable to configure STS endpoint when using ASSUME_ROLE credential provider in Kinesis connector

     [ https://issues.apache.org/jira/browse/FLINK-29496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Danny Cranmer updated FLINK-29496:
----------------------------------
    Fix Version/s: 1.17.0
                   1.15.3
                   1.16.1

> Unable to configure STS endpoint when using ASSUME_ROLE credential provider in Kinesis connector
> ------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-29496
>                 URL: https://issues.apache.org/jira/browse/FLINK-29496
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kinesis
>            Reporter: Aleksandr Pilipenko
>            Priority: Major
>             Fix For: 1.17.0, 1.15.3, 1.16.1
>
>
> 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)