Table Size growth and cost implication of using DynamoDb table for kinesis Stream Checkpointing

0

We are trying to use consume Kinesis Stream from Nifi and that requires us to use DynamoDb Table for Checkpointing at the source account. So a few question related to this effort.

  1. Can we use the DynamoDB table on the Consumer account instead of the Source Account ?
  2. How does this table grow eventually and what would be cost implication of the growth?
已提問 1 年前檢視次數 274 次
1 個回答
0

To use a DynamoDB table for checkpointing at the consumer account you will need to:

  • Create a new DynamoDB table in the consumer account that has the same structure as the checkpointing table in the source account.
  • Update the kinesis consumer code in Nifi to use the new DynamoDB table in the consumer account
  • Test the new configuration to ensure that checkpointing is working

Please make sure the correct permissions are updated to allow cross account access to the new DynamoDB. Please check with the Nifi documentation to get the exact permissions needed.

In response to the table growth, the database should remain stable so long as your shard count doesn't change. When shards rollover periodically, this number is briefly elevated, but if your application is processing at par with the throughput, it would go back down pretty fast.

AWS
支援工程師
Luke_D
已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南