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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to