AWS Amplify custom domain stuck on creating records and returning CloudFront 403

Question

Hello,

I have an issue with AWS Amplify custom domain setup for my app.

Domain: dating.date

Problem:
The custom domain setup is stuck on “Creating records associated with your domain...” for a long time.
When I open the domain in browser, I get a CloudFront 403 error:

“The request could not be satisfied.”

What I already checked:
- The domain was working earlier today with another Amplify app/repository.
- DNS is configured in Route 53.
- I removed old records and also tried a fresh hosted zone.
- I deleted and re-added the domain multiple times.
- I tested both root domain (dating.date) and www subdomain.
- I also tested redirect from root to www.
- No new ACM certificate is being created for this domain in us-east-1.
- The behavior looks like CloudFront is partially attached, but Amplify does not complete the domain association.

Question:
Is this a known Amplify issue or stale/orphaned domain association state?
What is the correct way to fully reset the domain association for dating.date so Amplify can attach it again?

This issue blocks production deployment.

Thank you.

Johan Staring · Answer

You may want to create a support case and work through this that way, but otherwise:
```
Root Cause: Orphaned CloudFront distribution still holds the dating.date CNAME
            from the previous Amplify app, blocking the new association.

Fix Path:
1. Find & clean orphaned CloudFront distribution CNAME  →  Check all accounts
2. Delete stuck domain association from current Amplify app
3. Clean Route 53 stale records
4. Wait 1-2 hours
5. Re-add domain to Amplify
6. If still stuck → AWS Support case (likely cross-account CNAME conflict)
```

AWS Amplify custom domain stuck on creating records and returning CloudFront 403

Añade tu respuesta

Contenido relevante