Anomalies in Cognito User Pool settings

Question

The problem is the reset of the pre sign-up cognito trigger lambda function(Node.js) . The trigger disappears from the selected one and is reset to 'None'.  I tried look into CloudTrail to see if anyone or anything is changing this setting but couldn't find anything. Any ideas on the places to look for logs to see what is the reason for this setting reset?  It happened in both prod and stage account twice already. Maybe is related to Amplify somehow?

Accepted Answer

Hi Daniel,

The issue you're experiencing is most likely related to the bug described here - https://github.com/aws-amplify/amplify-cli/issues/8997. Please follow the GitHub issue for further updates on the fix and workaround. Thanks!

Answer

Hi,

Do you have any automation (CloudFormation, CLI, API calls) that update the user pool using UpdateUserPool APIs? You can look in CloudTrail logs for UpdateUserPool events and inspect the input.

The behavior of this API is that all inputs need to be provided or otherwise default values will be used, the correct way to do that is to first call DescribeUserPool API, edit/add the settings that you would like to change then pass the entire payload to UpdateUserPool API call.

Anomalies in Cognito User Pool settings

Relevant content