Questions tagged with AWS Amplify

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Amplify - how to restart custom domain process?

We offer our customers the ability to create a full custom domain for our app, which is hosted on AWS Amplify. When a customer adds their custom domain, we add it to the Amplify app. Amplify then returns two DNS records which the customer must create: one with a CloudFront distribution domain as the value, and a second used to verify domain ownership. Amplify immediately starts attempting to validate the existence and correctness of these two DNS records. When found and verified, Amplify deploys the CloudFront distribution. All good at this point. However, if for some reason the customer make a mistake in the DNS records, Amplify will detect that and mark the domain as failed. Unfortunately, and as far as I know, even if the customer fixes the issue, there is now way to tell Amplify to attempt validation again. Instead, we can only delete the Amplify domain and re-create it. And here is the big problem: Amplify now creates a *different* CloudFront domain *and* starts the validation process immediately. Why is this a problem? Because even if we give the new domain to the customer right away, it will take them some time to make the change, and in any case the corrected value will take some time to propogate, so there will be a period when the old value is returned. So, Amplify immediatley sees the old incorrect DNS value again, and immediatley fails, again. As of now, I can only think of one solution -- first tell the customer to delete the old DNS values, then wait for DNS propogation, and only then create the Amplify domain, and give the customer the new DNS values. But, this is a really shitty experience for the customer. Anyone have any ideas on how we can better handle this situation? It would be awesome if Amplify simply provided a way to tell it to restart the validation process, with the same DNS values, but I've already created a feature request for that, an I'm not sure it will happen any time soon. Thanks for any info.
asked 7 days ago