Description at top of ChangeDataCapture/template.yml seems wrong - it's directly copied from ChangeDataCapture/template.yml

"Key attributes only", old and new"?

It appears that both the source and target DynamoDB tables use the "TargetRegion" parameter as the region. This is a problem if I want to replicate data to another DynamoDB table in another region

Hey, thanks for the nice replication guide and the SAM templates you prepared.
In the ChangeDataCapture step I just have the issue that the EventSourceMapping could not be created in my CloudFormation stack.

I am constantly getting an error like:

Resource handler returned message: "Invalid     
request provided: Cannot access stream          
arn:aws:kinesis:eu-                             
west-1:*****:stream/*****. Please ensure the role can perform   
the GetRecords, GetShardIterator,               
DescribeStream, ListShards, and ListStreams     
Actions on your stream in IAM. (Service: Lambda, Status Code: 400, Request ID: *****, Extended  
Request ID: null)" (RequestToken: *****,           
HandlerErrorCode: InvalidRequest)               
The following resource(s) failed to create:     
[ReplayFromStreamFnDDBEvent]. Rollback          
requested by user. 

I used the template as it came from this repository.

In UpdateObjectOwner.sh bucket-owner-full-control (Line 6) should be on Line 5. The new line causes an error when running the script from Mac

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.

The dynamodb stream is emitting it's changes in json string format, with binary values being base64 encoded. However when performing the putitem command through boto, these strings are assumed to be un-encoded and go through an additional base64 encoding.

I was able to resolve this by transforming the binary objects into their bytes representations before sending them through boto

        if event_name == 'REMOVE':
            keys_to_delete = record['dynamodb']['Keys']

            # Look for binary values b64 decode them back into bytes
            for key in keys_to_delete:
                for valType in keys_to_delete[key]:
                    if valType == 'B':
                        keys_to_delete[key][valType] = base64.b64decode(keys_to_delete[key][valType])

            dynamodb.delete_item(TableName=target_ddb_name,Key=record['dynamodb']['Keys'])
        else:
            #print("Putting item")
            item_to_put = record['dynamodb']['NewImage']

            # Look for binary values b64 decode them back into bytes 
            for property in item_to_put:
                for valType in item_to_put[property]:
                    if valType == 'B':
                        item_to_put[property][valType] = base64.b64decode(item_to_put[property][valType])
            dynamodb.put_item(TableName=target_ddb_name,Item=item_to_put)

Hi,

I'm a newbie here and first time to use this cross-account-amazon-dynamodb-replication.

I was able to follow the README instructions and successfully ran the following commands for Initial Load on my local linux machine:

sam build
sam deploy --guided

I assumed I deployed the template successfully.

I was wondering what's next step if I wanted to replicate data from source DynamoDB table to the target table.
Can you please advise?

Hello,

First of all thanks for creating this great sample! It is super helpful and saved us a lot of development efforts.

I noticed that currently the sample doesn't allow setting aws partition as an override parameter. I am based on China and most of our resources are located within aws-cn instead of aws.

I was able to manually update the template file as well as the lambda function to make our case work, but I could see how adding the ability to override partition could benefit future users, especially considering we have at least 3 partitions for AWS now: aws, aws-cn, aws-us-gov, and that list might grow in the future. (Similar to "TargeRoleName", "TargetRegion" maybe we can have "TargetPartition")

Thanks a lot and thanks again for this awesome sample!