1回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
Hi,
Have you tried using DisableKinesisStreamingDestinationCommand instead of the UpdateTableCommand?
It sounds like it should fit your use case requirements:
Stops replication from the DynamoDB table to the Kinesis data stream. This is done without deleting either of the resources.
You can use EnableKinesisStreamingDestinationCommand to re-enable the Kinesis stream:
Starts table data replication to the specified Kinesis data stream at a timestamp chosen during the enable workflow. If this operation doesn't return results immediately, use DescribeKinesisStreamingDestination to check if streaming to the Kinesis data stream is ACTIVE.
Regards
回答済み 1ヶ月前
関連するコンテンツ
- 質問済み 6年前