CNAMEAlreadyExists

Question

I am trying to associate a CNAME record in my route53 hosted zone to a CloudFront distribution and am seeing this error message:  
  
com.amazonaws.services.cloudfront.model.CNAMEAlreadyExistsException: One or more of the CNAMEs you provided are already associated with a different resource. (Service: AmazonCloudFront; Status Code: 409; Error Code: CNAMEAlreadyExists; Request ID: 3349d478-c36e-45aa-a658-8e0b7ef76d01; Proxy: null)  
  
I have no other cloudfront distributions. Please advise.  
  
Thanks

Answer

This has to do with attempting to use an S3 & Cloudfront deployment after using the amplify console kept failing at the build stage. Using python > 3.7 in lambdas caused a backend build error which was resolved using:   
  
https://github.com/aws-amplify/amplify-console/issues/595#issuecomment-761049327  
  
Erasing the S3 Cloudfront instances and erasing the custom domain from wihtin the amplify console then re-configuring it sorted out all the issues.  
  
The confusing part was an error message referencing the domain being associated with another cloudfront distribution when there was no other cloudfront distribution.

CNAMEAlreadyExists

相关内容