1 Answer
- Newest
- Most votes
- Most comments
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
answered 14 days ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago