[
https://issues.apache.org/jira/browse/FLINK-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386134#comment-15386134
]
ASF GitHub Bot commented on FLINK-4222:
---------------------------------------
Github user tzulitai commented on a diff in the pull request:
https://github.com/apache/flink/pull/2260#discussion_r71557572
--- Diff:
flink-streaming-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/util/AWSUtil.java
---
@@ -87,6 +93,8 @@ public static AWSCredentialsProvider
getCredentialsProvider(final Properties con
? new
ProfileCredentialsProvider(profileName)
: new
ProfileCredentialsProvider(profileConfigPath, profileName);
break;
+ case AUTO:
+ credentialsProvider = null;
--- End diff --
missing `break;` ?
> 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)
