- Newest
- Most votes
- Most comments
When you encounter the error "One or more of the domains you provided are already in use by another CloudFront distribution" for a domain you own, it means that domain is already configured as an alternate domain name (CNAME) on a CloudFront distribution that you don't control.
To identify which distribution is using your domain, you can use the AWS CLI command:
aws cloudfront list-conflicting-aliases --distribution-id <your-distribution-id> --alias <your-domain-name>
This will provide information about the conflicting resource, including a partial Account ID and Distribution ID of the resource currently using your domain.
Alternatively, you can use the newer command:
aws cloudfront list-domain-conflicts --domain <your-domain-name> --domain-control-validation-resource <your-distribution-id>
This will return details about the conflict including the resource type, resource ID, and account ID.
Unfortunately, if the domain is being used by a CloudFront distribution in another AWS account that you don't control, the standard solution is to contact AWS Support. This typically requires at least a Developer Support plan, which comes with an additional cost. AWS Support can help you claim ownership of your domain and resolve the conflict.
Before contacting support, you might want to check:
- If you recently deleted a CloudFront distribution using this domain, wait 15-48 hours for DNS caches to clear
- Ensure you don't have any AWS Amplify apps that might have created an internal CloudFront distribution using your domain
- Verify your DNS configuration is correctly set up
- Check that your SSL/TLS certificate is valid and properly configured for the domain
Sources
How can I claim a CNAME for my Cloudfront distribution? | AWS re:Post
CloudFront Deployment Fails | AWS re:Post
One or more of the CNAMEs you provided are already associated with a different resource. | AWS re:Post
CloudFront examples using AWS CLI - AWS SDK Code Examples
Find the source standard distribution or distribution tenant - Amazon CloudFront

"Ensure you don't have any AWS Amplify apps that might have created an internal CloudFront distribution using your domain" - that's exactly what happened. Thank you so much!