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

["Robert Metzger (JIRA)" <ji...@apache.org>]

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

Robert Metzger resolved FLINK-4222.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/a497ebc8

> 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
>             Fix For: 1.2.0
>
>   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)