I ran into this error after adding a certificate. It claimed that DNS was setup but it was still saying this after a few hours. It turned out the reason was that I didn’t setup DNS for the www subdomain. Personally, I didn’t want the www but couldn’t delete it so I ignored it. It turns out the certificate they generate includes it and it won’t deploy the certificate until www is setup. Setting up www in route 53 fixed the issue. I wish I could have just deleted www. I don’t need support but since I didn’t find this answer anywhere I thought I should post it just in case someone else runs into the same issue.
By default, yes, we’ll configure DNS and an SSL cert for both. If you want us to drop the cert for the www domain, do let us know .