You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Aniket Bhatnagar (JIRA)" <ji...@apache.org> on 2014/12/14 14:16:13 UTC

[jira] [Closed] (SPARK-3640) KinesisUtils should accept a credentials object instead of forcing DefaultCredentialsProvider

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

Aniket Bhatnagar closed SPARK-3640.
-----------------------------------
    Resolution: Not a Problem

Tested and Chris's suggestion of using EC2 IAM instance profile works fine.

> KinesisUtils should accept a credentials object instead of forcing DefaultCredentialsProvider
> ---------------------------------------------------------------------------------------------
>
>                 Key: SPARK-3640
>                 URL: https://issues.apache.org/jira/browse/SPARK-3640
>             Project: Spark
>          Issue Type: Improvement
>          Components: Streaming
>    Affects Versions: 1.1.0
>            Reporter: Aniket Bhatnagar
>              Labels: kinesis
>
> KinesisUtils should accept AWS Credentials as a parameter and should default to DefaultCredentialsProvider if no credentials are provided. Currently, the implementation forces usage of DefaultCredentialsProvider which can be a pain especially when jobs are run by multiple  unix users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org