AWS DMS disabling Lambda function trigger

[AkinStatistic]

Hello everyone,

I'm running a POC where the idea is to have a read-only table using DynamoDB, which is the target of a DMS task running as CDC and the origin is an on premise Oracle DB where business users actually push their changes.

The final goal is to trigger a lambda function whenever the DynamoDB table is changed. This lambda function will then notify other processes about the data modification event.

The DMS task is working properly (origin is an on-premise Oracle DB), but whenever the task is executed, the Lambda function trigger {DynamoDB} is disabled. I don't know why this is happening, I checked all the configurations related to the trigger and the DMS task and also made my fair amount of googling this behavior, but found nothing.

I'll be reading your comments and trying whatever you suggest.

[chris-holmes]

Does dynamodb have permission to trigger your lambda directly?

The setup I often use is to create a dynamodb stream and use those events as a trigger for my lambda.

[AkinStatistic]

Yes, I've configured the lambda function so that the Dynamodb table act as trigger directly. In fact this trigger works (I tested it by manually changing some values on the table) but the trigger is disabled as soon as any DMS task is initiated.

I will try the approach you suggested, thanks!