If you're experiencing issues with your AWS services, then please refer to the AWS Health Dashboard. You can find the overall status of ongoing outages, the health of AWS services, and the latest updates from AWS engineers.
CloudFront Deployment Fails
Hi,
I'm trying to deploy a CloudFront distribution with a custom domain and I’ve configured the Alternate Domain Names (CNAMEs) in the distribution settings.
However, I get the following error during deployment:
What is the possible root cause of this error any Any Solutions to fix this?
- Newest
- Most votes
- Most comments
This error indicates that the domain name you're trying to use as an alternate domain name (CNAME) in your CloudFront distribution is already associated with a different CloudFront resource. This happens because each domain name configured for a CloudFront distribution must be globally unique to that distribution.
There are several possible causes and solutions:
- Previous Distribution Using the Same Domain: If you recently deleted a CloudFront distribution that used this domain name, DNS records might still be pointing to the old distribution. You should:
- Delete the DNS record for this domain
- Wait approximately 15 minutes for DNS caches to clear
- Create your new CloudFront distribution
- Once the new distribution is deployed and has its unique DNS name, create the CNAME or A/AAAA alias records in your DNS zone
- Domain Used by Another AWS Account: The domain might be configured in a CloudFront distribution owned by a different AWS account. You can verify this using the AWS CLI command:
aws cloudfront list-conflicting-aliases --distribution-id <your-distribution-id> --alias <your-domain-name>
This will show you the account ID and distribution ID that's currently using the domain.
-
DNS Configuration Issues: Ensure your DNS settings are correctly pointing to your intended CloudFront distribution and not to another AWS resource like an Elastic Load Balancer.
-
Certificate Issues: Make sure you have a valid SSL/TLS certificate for your domain:
- The certificate must be in the US East (N. Virginia) region (us-east-1)
- It must be properly formatted and include the complete certificate chain
- The certificate must cover the domain name you're trying to use
If you've verified all these points and are still experiencing issues, you might need to wait longer for DNS propagation (which can take up to 48 hours in some cases) or contact AWS Support for further assistance.
Sources
I remove my cloudfront deployment and create it again. But, When i create new deployment and use my prev domain, it can't access and error is occured. | AWS re:Post
One or more of the CNAMEs you provided are already associated with a different resource | AWS re:Post
CloudFront Incorrect Certificate | AWS re:Post
Hello.
Does the SSL certificate you set up on CloudFront match the alternative domain?
Or does the SSL certificate cover the alternative domain as a wildcard domain?
Judging from the error message, it seems there is a problem with the SSL certificate settings.
I recommend that you go through all the troubleshooting steps outlined in the following documents:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/troubleshooting-distributions.html#troubleshooting-distributions-certificates
Relevant content
- asked a year ago
