GuardDutytoACL-GuardDutytoACLDDBTable not updated with new rule about amazon-guardduty-waf-acl

[cgulliver]

Have you tried removing all entries in the DDB table and the associated NACL(s)? Can you confirm there is only a single instance of the solution running? Can you also share the logging info from the pruning Lambda function?

[e86h90]

As a test I set the Reserve Concurrency of the GuardDutytoACL-GuardDutytoACLLambda to 1. Throttling the lambda function in this manner has resolved the issue I have been having. The dynamodb state table and the Network ACL list have been in sync ever since.

[cgulliver]

Thanks for the update.

[cgulliver]

We have updated the Lambda code for this sample. A simple way to test is delete the associated entries in NACL's, WAF IP Sets and clear the DDB table, then replace the code in the lambda functions GuardDutytoACL-GuardDutytoACLLambda and GuardDutytoACL-PruneOldEntriesLambda with the new code... https://github.com/aws-samples/amazon-guardduty-waf-acl/tree/master/lambda. Would greatly appreciate feedback if this resolves your issue or not.