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 2023/04/24 14:39:00 UTC

[jira] [Commented] (FLINK-22828) Allow using a custom AWS credentials provider for the Kinesis Connector

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

Danny Cranmer commented on FLINK-22828:
---------------------------------------

Merged commit [{{17820d0}}|https://github.com/apache/flink-connector-aws/commit/17820d062007a4fcdf24c3b974c636f32705cd27] into apache:main

> Allow using a custom AWS credentials provider for the Kinesis Connector
> -----------------------------------------------------------------------
>
>                 Key: FLINK-22828
>                 URL: https://issues.apache.org/jira/browse/FLINK-22828
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kinesis
>    Affects Versions: aws-connector-4.1.0
>            Reporter: Arvid Heise
>            Assignee: Emre Kartoglu
>            Priority: Major
>              Labels: auto-unassigned, pull-request-available
>             Fix For: aws-connector-4.2.0
>
>
> Users currently have to use the credential providers that are pre-configured in Kinesis connector. 
> For advanced users, it would be nice to be able to configure it similar to Presto: https://prestodb.io/docs/0.187/connector/hive.html#custom-s3-credentials-provider



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