Skip to content

Amplify custom domain stuck FAILED - "alias points to another CloudFront distribution" - orphaned internal distributions

-1

App ID: d2d3bj1p216a32 Region: us-east-1 Domain: milocare.org

Problem:

Every attempt to associate milocare.org as a custom domain in Amplify fails with:

│ "One or more aliases specified for the distribution includes an incorrectly configured DNS record that points to another CloudFront distribution."

The www.milocare.org subdomain always verifies successfully (verified: true), but the apex milocare.org always fails.

Root cause identified:

Multiple failed association attempts created internal Amplify-managed CloudFront distributions that still hold milocare.org as an alias:

  • d1p94cnm58g0zy.cloudfront.net
  • d2yz568mfknxjh.cloudfront.net
  • d16ayqdswj8o8u.cloudfront.net

Each new association attempt gets a new distribution, but the previous ones are never cleaned up, causing the conflict.

What I've tried:

  • Deleting and recreating the domain association multiple times
  • Using AMPLIFY_MANAGED and CUSTOM certificate (arn:aws:acm:us-east-1:013960777529:certificate/ed2d22fd-ebb4-4913-80bf-415a06e0d900, Status: ISSUED)
  • DNS is correctly configured (Cloudflare, verified externally)

Request:

Please remove milocare.org as an alias from all orphaned Amplify-managed CloudFront distributions so the domain association can complete successfully.

1 Answer
0

I understand you're experiencing a frustrating issue where your Amplify custom domain association is failing because the apex domain appears to be associated with orphaned CloudFront distributions from previous failed attempts.

This is a known scenario that can occur when domain association attempts fail partway through the process, leaving behind CloudFront distributions that still hold the domain as an alternate domain name (CNAME). Since CloudFront doesn't allow the same alternate domain name to be associated with multiple distributions, subsequent attempts fail with the alias conflict error you're seeing.

Here's what you should do:

  1. Contact AWS Support directly through the AWS Support Center at https://console.aws.amazon.com/support/. This issue requires backend intervention to clean up the orphaned CloudFront distributions that are holding your domain alias. Support engineers have the tools to identify and remove these associations safely.

  2. In your support case, provide:

  • Your Amplify App ID
  • The specific domain experiencing the issue
  • The CloudFront distribution IDs you've identified (if you have them)
  • Confirmation that you've verified DNS is correctly configured
  1. While waiting for resolution, avoid creating additional domain association attempts, as each failed attempt may create another orphaned distribution, compounding the problem.

Important note about your certificate: Since you mentioned trying both AMPLIFY_MANAGED and a custom ACM certificate, ensure that any custom certificate you use is in the us-east-1 region (which yours appears to be) and includes both the apex domain and www subdomain as Subject Alternative Names.

The AWS Support team will be able to identify the internal Amplify-managed distributions and remove the conflicting aliases so your domain association can proceed successfully. Depending on your AWS Support plan, response times may vary, so consider reviewing your support plan options if you need faster assistance.

answered 3 months ago

EXPERT

reviewed 3 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.