1 Answer
- Newest
- Most votes
- Most comments
0
Hi Vince, you should decompose the issue by trying to run the lambda that you created through CLI invoke with payload that you tailored manually.
See https://awscli.amazonaws.com/v2/documentation/api/latest/reference/lambda/invoke.html
The payload that your manual should provide is described here: https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-lambda-post-confirmation.html#cognito-user-pools-lambda-trigger-syntax-post-confirmation
When you get your lambda to work properly in those manual invocations, you can go back to Cognito and try to trigger it via Cognito to see what happens.
Hope it helps Didier
Relevant content
- asked 2 years ago
- asked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
Will give it a try and report back.
Oddly the lambda worked fine right away, Multiple attempts to get the cognito trigger to fire failed after adjusting permissions on the console multiple times. More testing...