- Newest
- Most votes
- Most comments
You may identify the conflict by checking other Amplify Apps, CloudFront Distributions, ACM Certificates and Roue53 Records, you may then try t clean up DNS records in Route 53 to see whether this can help.
Hey,
Hope you're keeping well.
That error usually means the CNAME validation records for the ACM certificate are still tied to another CloudFront distribution or Amplify app. In Route 53, check the hosted zone for any _acm-validation CNAME records and delete or update them so they match the new certificate Amplify is provisioning. Also verify in the ACM console (same region as Amplify) that no other certificate is using the same domain name, and remove old certificates if they’re no longer needed. Once the DNS is cleared, retry adding the custom domain in Amplify so it can create fresh validation records.
Thanks and regards,
Taz
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
