- Newest
- Most votes
- Most comments
This is a common issue when trying to reuse a domain with AWS Amplify after previously using it with another app. Even though you've deleted the previous app and cleared Route53 records, the association between your domain and the CloudFront distribution might still exist in AWS's systems.
Here are steps to resolve this issue:
- Check for conflicting CloudFront distributions using the AWS CLI:
aws cloudfront list-conflicting-aliases --distribution-id <your-new-distribution-id> --alias gifted-project.net
This will show if there's a conflicting distribution and in which account it exists.
-
Wait longer: Sometimes these issues resolve themselves after 24-48 hours as AWS systems update. In some cases, it might take up to 6 hours for the system to fully clear previous associations.
-
Verify DNS propagation: Use tools like dig or nslookup to ensure all old DNS entries are completely removed and propagated.
-
Try alternative domain management: You could try using AWS Certificate Manager (ACM) to manage your SSL certificates separately and then link them to your Amplify app.
-
Contact AWS Support: If none of the above works after waiting for at least 6 hours, you'll need to contact AWS Support to help clear any hidden associations with your domain name. You can do this through the "Account and billing" support channel, which is free.
The key issue is that each custom domain name must be unique across all CloudFront distributions globally, not just within your account. This is why you can encounter this issue even when you don't see any distributions in your own CloudFront console. AWS Support can help release the domain from any lingering associations in their internal systems.
Sources
CNAME problem deploying a custom domain in Amplify | AWS re:Post
One or more domains requested are already associated with another Amplify | AWS re:Post
One or more of the CNAMEs you provided are already associated with a different resource | AWS re:Post
Can't Activate AWS Amplify Custom Domain | AWS re:Post
Relevant content
- AWS OFFICIALUpdated 4 years ago
