Open niklaswallerstedt opened 3 years ago
It seems like this is a limitation of the Cognito backend service that does not let user pool domain be updated.
Can you try a 2-stage deploy? First, remove the addDomain()
method call from your CDK app and deploy, then, add the addDomain()
back but with the new settings and deploy again.
Yeah, I tried that workaround when I was trying to update the domain and it works.
I was posting the bug report because I felt that it didn't behave as I was expecting it to.
Internal tracking: i/CFN-33216
It seems like this is a limitation of the Cognito backend service that does not let user pool domain be updated.
Can you try a 2-stage deploy? First, remove the
addDomain()
method call from your CDK app and deploy, then, add theaddDomain()
back but with the new settings and deploy again.
The 2 stage deployment worked with me, weird that the cdk has this issue
I've reached out on the original ticket posted by niranjan. Hopefully will get a response soon
The inability to update domainPrefix
is blocking us (AWS Amplify) from replacing our custom lambda callout with proper CFN resource.
The workaround in form of 2 deployments is not feasible for us.
Can we get this bug fixed ?
I wanted to change the hosted UI domain prefix after an initial deploy (
userPoolCognitoDomainPrefix
), but I'm getting a 400 on subsequent deploys. (I've just recently started to work with Cognito with CDK, so there might be some constraints in Cognito I'm not aware of. Keep up the good work!)Reproduction Steps
What did you expect to happen?
The domain should update and remove the old one as it's no longer specified.
What actually happened?
Environment
Other
This is :bug: Bug Report