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

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

GitHub user chadnickbok opened a pull request:

    https://github.com/apache/flink/pull/2260

    [FLINK-4222] Allow Kinesis configuration to get credentials from AWS 
Metadata       

    When called without credentials, the AmazonKinesisClient tries to configure 
itself automatically, searching for credentials from environment variables, 
java system properties, and finally from instance profile credentials delivered 
through the Amazon EC2 metadata service.
    
    Add the AWSConfigConstant "AUTO", which supports creating an 
AmazonKinesisClient without any AWSCredentials, which allows for this 
auto-discovery mechanism to take place and supports getting kinesis credentials 
from the AWS EC2 metadata service.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chadnickbok/flink aws-metadata-auth-kinesis

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2260.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2260
    
----
commit 8d43f05ce65b88067fd5a4808c773cafc693c0f2
Author: Nick Chadwick <[email protected]>
Date:   2016-07-15T23:24:19Z

    Support automatic AWS Credentials discovery.
    
    When called without credentials, the AmazonKinesisClient tries to configure 
itself automatically, searching for credentials from environment variables, 
java system properties, and finally from instance profile credentials delivered 
through the Amazon EC2 metadata service.
    
    Add the AWSConfigConstant "AUTO", which supports creating an 
AmazonKinesisClient without any AWSCredentials, which allows for this 
auto-discovery mechanism to take place and supports getting kinesis credentials 
from the AWS EC2 metadata service.

----


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

Reply via email to