Question:
I’m triggering a Lambda when a user registers to make an entry to a database. Post Confirmation Lambda Trigger triggers fine, there are no problems with it. Now, after implementing a password change form I’m seeing the same Lambda triggered.
In fact, AWS states that it should – it’s “Post Confirmation” and so when the user confirms his email retyping sent code, it triggers. I’m fine with that.
How to recognise, in the Lambda, what was the reason for firing the trigger? I don’t want to make the same DB calls when it’s just a password change.
(I checked the request coming in – there’s nothing useful for that problem there)
Answer:
To differentiate the source on a PostConfirmation, you have to use the "triggerSource": "string" attribute in the event object.
The trigger source can be PostConfirmation_ConfirmForgotPassword or PostConfirmation_ConfirmSignUp for a PostConfirmation.
The event object will be of the format:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
{ "version": "string", "triggerSource": "string", "region": AWSRegion, "userPoolId": "string", "userName": "string", "callerContext": { "awsSdkVersion": "string", "clientId": "string" }, "request": { "userAttributes": { "string": "string", .... } }, "response": {} } |