2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
If your view is similar to below, then ensure that you enable a DynamoDB stream on at least one table.
If you don't get that far, ensure the role you are creating the trigger with has the necessary DynamoDB roles, such as ListTables/DescribeTable/ListStreams/DescribeStream
0
Does your Lambda have the proper policy in place? Your lambda needs to have access to the following operations on the dynamodb db stream arn
["dynamodb:GetRecords", "dynamodb:GetShardIterator", "dynamodb:DescribeStream", "dynamodb:ListStreams"]
con risposta 6 mesi fa
I have updated the question by including the image. Hopefully u can help me to solve it. Thank you~
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
I have updated the question by including the image. Hopefully u can help me to solve it. Thank you~
Your role needs the permissions I mentioned.