We need to give AWS Amplify a fighting chance
vaughan mason - 2021-05-18So going through the process of creating a static website on AWS
We are sitting in a bit of a waiting game with the SSL and the domain verification, it was a lot simpler on Azure for a third-party website verifications.
So I may have done this wrong, it was a little confusing as AWS determines ownership first before it does DNS activation. Actually having to read the documentation to get this one right. The thing is when I did this step on Azure, it was simple and straight forward. If this does not work I am giving up
Documentation DNS Verification Crazy not simply
So I partially blame myself and AWS, their documentation was not fully aligned to what need to be done.
It is working now, and must have recreated the dns settings on website a couple of times. Editing DNS records is a dark art.
Going to complete the build process whilst we wait. Okay that has been done. This is a little ridiculous.
Verifications has gone over 15 mins, Azure site was up by now.
This page was last updated at 2021-05-18
If you don't agree with the content on this page, please click here