Select Language:
If you’re facing a problem setting up a custom domain in AWS Amplify, especially when the process seems stuck on “Creating records associated with your domain…” for a long time, here’s a straightforward way to resolve it.
First, check your DNS settings in Route 53. Make sure that the DNS records are correctly pointing to AWS and that there are no conflicting entries. Since you’ve already tried removing old records and creating a new hosted zone, you can proceed to fully reset the domain association.
To do this, remove the custom domain from your AWS Amplify app entirely. Then, go into Route 53 and delete any existing DNS records related to that domain. Afterward, wait a few minutes to ensure all changes are registered.
Next, re-add the domain in Amplify as if it’s a new setup. When prompted, confirm that your DNS records are correctly configured in Route 53. Amplify will generate new CNAME or A records—make sure to add them as instructed.
Now, give it some time for the records to propagate. If the setup still gets stuck, there might be an orphaned or stale association causing issues. To clear that, you should:
– Remove the domain from the Amplify app.
– Delete all DNS records related to the domain in Route 53.
– Wait for the DNS changes to fully propagate.
– Re-attach the domain in Amplify, ensuring the correct records are in place.
It’s also a good idea to check the SSL certificate creation status in AWS Certificate Manager (ACM), especially if no new certificates are being issued. Sometimes, issuing a new certificate or manually requesting one can help if the automatic process stalls.
By completely resetting the domain association and making sure your DNS records are accurate, you give Amplify a clean slate to attach the domain successfully. This approach often resolves issues where Amplify gets stuck during domain setup and prevents deployment delays.
Hope this helps you move forward with your deployment!
ChatGPT
Perplexity
Gemini AI
Grok AI
