dapr / dapr/docs

Binding AWS Kinesis - Indicate that a DynamoDB Table is Needed, and how it is named

Open
#4,328 0 comments 0 reactions 0 assignees View on GitHub
content/missing-information
Dominant language
SCSS
Stars
1k
Forks
794
Avg merge
2d 8h
Merged PRs (30d)
7

Description

**What content needs to be created or modified?**
Clarification and additional details about a potential dynamodb table creation and changes to credentials

**Describe the solution you'd like**

A blurb or two about:
1. That this binding uses the KCL from vmware
2. The KCL requires? a dynamodb table. Will create automatically and will have the same name as the `consumerName` value in the config
3. If this components-contrib [issue](https://github.com/dapr/components-contrib/issues/3508) is resolved, then perhaps an update to how the credentials are fetched will be needed.

**Where should the new material be placed?**
On the components-reference page [here](https://docs.dapr.io/reference/components-reference/supported-bindings/kinesis/)

**The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos**
Relevant [PR](https://github.com/dapr/components-contrib/pull/3509) in components-contrib

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.