I had originally thought that this issue was due to mismatching regions, but after changing the region, I\'m still coming across the following error when trying out an Amazon AW
In my case, my table name included a "/" character, which is invalid. Removing the "/" character from the table name resolved the issue.
You can instead assign permission to the lambda's role like this:
Worked with an Amazon engineer and it turns out the problem was in the policy configuration:
"dynamodb: *"
should be
"dynamodb:*"
It's amazing what a space can do.