DynamoDB tables replication blocked with lambda out of memory

We build CDC solution on AWS Account.
For some frequently updated DDB tables , we find that the target dynamoDB table has no data imported. We checked the lambda logs . The logs show as follow

As we can see, the lambda default 128M memory are used up. we update lambda memory size by aws cli and the replication recovered.

`aws lambda update-function-configuration \
--function-name my-function \
--memory-size 256
`

Solutions Suggestion:
1.Expose lambda Memory size as parameter in sam template.

2.furthor more, It will be better if we add sns notification with lambda error logs ,So that people can receive alarm mail in time.

Start by locating the SAM template that defines the replication Lambda and review the Lambda logs and the shown AWS CLI configuration change. Define the requested scope: exposing memory size as a template parameter, and whether SNS notification for Lambda errors is also included. Done means the replication can use a higher configured memory size and the agreed error notification behavior works.

Written by the indexing model from the issue text.