[jira] [Commented] (SPARK-10969) Spark Streaming Kinesis: Allow specifying separate credentials for Kinesis and DynamoDB

["Grega Kespret (JIRA)" <ji...@apache.org>]

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

Grega Kespret commented on SPARK-10969:
---------------------------------------

I believe this is now possible through the {{KinesisInputDStream.Builder}} class as:

{code}
KinesisInputDStream.builder
  ...
  .kinesisCredentials(creds1)
  .dynamoDBCredentials(creds2)
  .cloudWatchCredentials(creds3)
  .build
{code}

Close the ticket?

> Spark Streaming Kinesis: Allow specifying separate credentials for Kinesis and DynamoDB
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-10969
>                 URL: https://issues.apache.org/jira/browse/SPARK-10969
>             Project: Spark
>          Issue Type: Improvement
>          Components: DStreams
>    Affects Versions: 1.5.1
>            Reporter: Christoph Pirkl
>            Priority: Critical
>
> {{KinesisUtils.createStream()}} allows specifying only one set of AWS credentials that will be used by Amazon KCL for accessing Kinesis, DynamoDB and CloudWatch.
> h5. Motivation
> In a scenario where one needs to read from a Kinesis Stream owned by a different AWS account the user usually has minimal rights (i.e. only read from the stream). In this case creating the DynamoDB table in KCL will fail.
> h5. Proposal
> My proposed solution would be to allow specifying multiple credentials in {{KinesisUtils.createStream()}} for Kinesis, DynamoDB and CloudWatch. The additional credentials could then be passed to the constructor of {{KinesisClientLibConfiguration}} or method {{KinesisClientLibConfiguration.withDynamoDBClientConfig()}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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