Amplify custom domain stuck on SSL configuration

I was having this same issue, and it turned out that my NS records listed under "Hosted zones" didn't match those under "Registered domains." All this is on the Route 53 dashboard. So I updated the ones under "Registered domains" and now everything is working.

After almost 48 hours of deploying, deleting, redeploying, and rehosting, several times, it turned out the NS records in my Hosted zones was entirely different from those in my Registered Domain, please make sure they match, else it would freeze in SSL configuration as it did for me almost 48-72hours nearly turning me into some that don't know what he is doing. Just compare your Registered Domain NS record and Hosted zones NS record and update with that of Hosted zones, because that is where AWS automatically creates your CNAME records. Hope this helps someone who might have the issue.

I'm having this same issue I believe (just posted about it on here).

Did you ever figure out a solution?

I'm having the same issue. I've double checked everything is correct on my domain records, and it's been stuck in the SSL configuration stage for over 24 hours. Any ideas on what to try differently?

Experiencing this too...It's been more than 48 hours. I tried removing app, redeploying and then adding my custom domain again. CNAME is propagating so not sure what to do at this point...it's been a while.

I don't have nothing under Registered domains nor in the Hosted zones, because I have never done any configuration there. It's not required for Amplify to work. I keep having the same problem. Has anyone solved it? Thank you.

Edited by: MartinAristizabal on Dec 15, 2020 6:19 PM

I solved it!. The thing is that there is a specific configuration for Godaddy in my case, that differ from the ones by default in the instructions. I followed the "Troubleshooting guide" in the Custom Domain configuration and now my domain is working OK. Other cases could be similar to these.

I also stuck to the same problem. In my case for NameCheap what needs to be done instead of "Configure a CNAME to point to the AWS validation server" as in trouble shoot was to specify nameservers in my AWS account(Route 53) in NameCheap configuration. after the configuration is done, as fast as within 10mins, the domain is activated in Amplify console.
DNS config is always a pain in the ass as it's always stated that "it might take up to 24 hours" or so on.
Hope this might help someone who ends up here!

https://www.namecheap.com/support/knowledgebase/article.aspx/10371/2208/how-do-i-link-my-domain-to-amazon-web-services/

Edited by: RouterKiez on Sep 7, 2021 11:01 AM