flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4222) Allow Kinesis configuration to get credentials from AWS Metadata
Date Fri, 19 Aug 2016 00:08:21 GMT

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

ASF GitHub Bot commented on FLINK-4222:
---------------------------------------

Github user tzulitai commented on the issue:

    https://github.com/apache/flink/pull/2260
  
    @rmetzger Sure, that would be great. Thanks for your help with merging this.
    Thanks for your contribution @chadnickbok :)


> Allow Kinesis configuration to get credentials from AWS Metadata
> ----------------------------------------------------------------
>
>                 Key: FLINK-4222
>                 URL: https://issues.apache.org/jira/browse/FLINK-4222
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming Connectors
>    Affects Versions: 1.0.3
>            Reporter: Nick Chadwick
>            Priority: Minor
>              Labels: easyfix
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When deploying Flink TaskManagers in an EC2 environment, it would be nice to be able
to use the EC2 IAM Role credentials provided by the EC2 Metadata service.
> This allows for credentials to be automatically discovered by services running on EC2
instances at runtime, and removes the need to explicitly create and assign credentials to
TaskManagers.
> This should be a fairly small change to the configuration of the flink-connector-kinesis,
which will greatly improve the ease of deployment to Amazon EC2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message