# Kinesis input plugin - Configure Kinesis and DynamoDB using different AWS profiles

**URL:** <https://discuss.elastic.co/t/kinesis-input-plugin-configure-kinesis-and-dynamodb-using-different-aws-profiles/156111>\
**Category:** Logstash\
**Created:** [November 9, 2018, 9:51pm UTC](https://discuss.elastic.co/t/kinesis-input-plugin-configure-kinesis-and-dynamodb-using-different-aws-profiles/156111 "2018-11-09T21:51:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vijay\_Reddiar](https://avatars.discourse-cdn.com/v4/letter/v/2acd7d/32.png) [@Vijay\_Reddiar](https://discuss.elastic.co/u/Vijay_Reddiar)\
**Post date:** [November 9, 2018, 9:51pm UTC](https://discuss.elastic.co/t/kinesis-input-plugin-configure-kinesis-and-dynamodb-using-different-aws-profiles/156111/1 "2018-11-09T21:51:07Z")

</div>

Kinesis input plugin is working great but now I am running into an security issue. In my integration scenario for monitoring the flow logs, I have to consume the Kinesis stream hosted by the client. Client security policies does not allow to create dynamo db table for worker coordination, I still did not invested time in KCL but looking for a COTS solutions that can use different AWS profile for dynamo db requirements while reading the records from Kinesis. Thanks in advance for all your help.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 7, 2018, 9:51pm UTC](https://discuss.elastic.co/t/kinesis-input-plugin-configure-kinesis-and-dynamodb-using-different-aws-profiles/156111/2 "2018-12-07T21:51:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.