You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/18 14:39:23 UTC

[jira] [Commented] (FLINK-4222) Allow Kinesis configuration to get credentials from AWS Metadata

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

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

Github user rmetzger commented on the issue:

    https://github.com/apache/flink/pull/2260
  
    Thanks a lot for the review @tzulitai.
    @chadnickbok Thanks a lot for the contribution!
    
    I can also offer to add the missing `break;` when merging the PR.


> 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)