1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a 23 jours
Contenus pertinents
- demandé il y a 7 mois
- demandé il y a 9 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 4 ans