If you’re having trouble attaching your custom domain to Amplify because it seems to be linked to leftover CloudFront distributions from previous failed attempts, you’re not alone. This happens when a domain association doesn’t finish properly, leaving behind CloudFront setups that still list your domain as an alternate name (CNAME). Since CloudFront doesn’t let multiple distributions use the same alias, subsequent try attempts often result in errors about alias conflicts.
Here’s how you can resolve this issue:
First, reach out to AWS Support through the AWS Support Center. Explain the problem and ask them to assist in cleaning up the orphaned CloudFront distributions that might be holding your domain. They have the tools needed to safely identify and remove these leftover associations.
When you contact support, be sure to include:
– Your Amplify App ID
– The exact domain you’re trying to set up
– Any CloudFront distribution IDs you’ve found related to this issue
– Confirmation that your DNS settings are correctly configured
While you’re waiting for support to help, avoid trying to add your domain again. Each failed attempt can create more orphaned distributions, making the problem worse.
If you’re using a custom SSL certificate, remember it needs to be in the US East (N. Virginia) region. Also, ensure the certificate includes both your root domain and www subdomain as Subject Alternative Names.
The AWS support team will work to identify the conflicting distributions and remove the problematic aliases, allowing your domain association to go through smoothly. Response times can vary depending on your support plan, so consider upgrading if you need quicker help.