- Newest
- Most votes
- Most comments
The issue you're experiencing is likely related to how Amplify manages CloudFront distributions and domain associations behind the scenes. When you set up a custom domain in Amplify, it creates and manages a CloudFront distribution automatically. The error about the DNS record pointing to another CloudFront distribution, followed by the AmplifyWaitTimeout error, suggests there may be a conflict or stale association.
Here are the AWS-side steps you can take to resolve this:
First, try removing the custom domain from your Amplify app completely, then wait a few minutes before re-adding it. This allows Amplify to clean up the underlying CloudFront distribution and domain associations. When you re-add the domain, Amplify will create a fresh CloudFront distribution with the proper configuration.
If the domain was previously associated with another Amplify app in your account (or even a different AWS account you have access to), you'll need to remove it from that app first. Check all your Amplify apps across all regions to ensure the domain isn't already claimed elsewhere.
For the AmplifyWaitTimeout error specifically, this typically occurs when Amplify cannot verify the CNAME record within its expected timeframe. Even though public DNS lookups show the correct resolution, DNS propagation can take time, and Amplify's verification checks may be hitting DNS servers that haven't updated yet. After ensuring your CNAME is correctly configured, give it additional time (up to 48 hours in some cases) for full DNS propagation.
Make sure you're adding the CNAME record exactly as Amplify specifies, without any trailing dots or additional formatting that your DNS provider might add automatically. Some DNS providers add the domain suffix automatically, which can cause the record to be created incorrectly.
If you continue to experience issues after removing and re-adding the domain, you may need to reach out to AWS Support through the AWS Support Center to investigate whether there's a backend issue with the CloudFront distribution or domain association that requires manual intervention.
Relevant content
asked a year ago
asked a year ago
Thanks. Before I delete and recreate the domain association, could an AWS Support Engineer confirm whether this may be an orphaned Amplify-managed CloudFront alias? Another re:Post case with the same symptoms indicates the alias may exist in an AWS-owned account and cannot be released by the customer. My public DNS, ACM validation CNAME and CAA checks are already correct.