...

[ghost]

[rawnsley]

Are any of the CNAMES you are trying to use associated with other resources in AWS? It might not be CloudFront, they could be fronting a lamda or an S3 bucket I guess. I would start in Route53 and check the domain isn't obviously associated with any services then I would try Google for that error in the hope that you can somehow search AWS for services by CNAME association.

[rawnsley]

Possibly similar problem here #3568

[ghost]

unfortunately not. i found that yesterday and it didn't provide me any help.

[rawnsley]

That's not how I do it (I have three domains), but Recipe 1 says it's OK. For Domain Name, have you tried both lokaverse.click and hub.lokaverse.click?

[ghost]

i'll try running the installer again with hub.lokaverse.click

[ghost]

i give up. there's something wrong with the cloudformation script provided.

[robinkwilson]

If you run the stack twice -- or used the domain for something else, sometimes cleanup doesn't delete CNAMEs and/or the Cloudfront resource / other resources associated on your domain.

When I run into this issue:

1. Check Cloudfront in AWS to see if any running resources are there (*Check your stack region! AND check in N. Virginia region just in case ). Sometimes I find a running resource, and sometimes there's nothing.
2. Delete the Cloudfront resource -- if you can determine which CNAME hash matches the resource, note it.
3. Go to Route 53 and select the domains.
4. ** WARNING ASK YOURSELF are you using the domain for anything else? If so, DO NOT DELETE ANY CNAME RECORDS. You need to BE SURE that the records you delete do not have prior functionality. HOWEVER, if you are ONLY using these domains for Hubs Cloud then follow the next steps... **
5. (SEE STEP # 4) BE VERY CAREFUL! Delete only the extra CNAMES on your domains. DO NOT DELETE A records or any other records.
6. Try the deploy again.

I run into this AWS error often because I reuse the same domains for my Hubs Cloud stacks. Sometimes cleanup doesn't completely finish/or CNAMEs are left over. AWS stops the stack creation process as a safeguard to ensure the domain you're using is only being used for one purpose and don't get extra side effects.

Let me know how it goes.

[ghost]

thanks for posting this, but i have already done this multiple times. if there are no other suggestions i think i'll move on from trying to use this.