-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS::Cognito::UserPool LambdaVersion does not get set correctly #406
Comments
I have just had a thought, as the pre token generation lambda was deployed initially with the key PreTokenGeneration there may be an issue with the backwards capability. I will try completely removing the pre token generation lambda from the template then re-adding it to see if that fixes the problem. If it does I will raise a ticket in Cognito support. |
Having removed the pre token generation lambda completely deploying, then re-adding and deploying gives the same result of the pre token generation lambda being version V1_0. |
Due to inactivity this issue will be closed in 7 days |
Which sample template is this about? |
Due to inactivity this issue will be closed in 7 days |
I am setting the value for AWS::Cognito::UserPool LambdaConfig PreTokenGenerationConfig LambdaVersion to 'V2_0'.
I have checked the cloudformation template in the console and it is being correctly set. However, the Cognito pre token generation lambda version is set to V1, I have checked both in the console and by attempting to use the new features.
I am able to set the version to 2 in the console and it works as intended.
Additional information: Using the serverless framework to deploy, although this shouldn't matter as the value is being set correctly confirmed in the console.
The text was updated successfully, but these errors were encountered: