Trouble with Static Site + Custom domain #5543
Replies: 2 comments 6 replies
-
Hello @Caio-Domingos. This looks strange to me 🤔 Can you help me check the route53 record for |
Beta Was this translation helpful? Give feedback.
-
Hello, After conducting extensive testing, I have come to some intriguing conclusions that I would like to share for further insights. I created an application named "ga-awscop" and an environment "develop" to test some deployments. AWS Copilot, behind the scenes, created two hosted zones in Route 53: "ga-awscop.thinkless.com.br" and "develop.ga-awscop.thinkless.com.br". Here's what I found:
Initially, I thought it might be an issue with the VPC of the environment, but this didn't make sense since a Static Site type service doesn't typically involve VPC interactions, as it's a straightforward S3 -> Cloudfront -> Route 53 (Alias) -> World process. So, I ruled out the VPC issue. Here are the specific tests I conducted and their outcomes:
This leads me to believe that these hosted zones, specifically "develop.ga-awscop.thinkless.com.br" and "caio-testes.thinkless.com.br", although created, are non-functional for some reason beyond my current understanding as a developer. What are your thoughts on this? Any insights or suggestions would be greatly appreciated. Thank you. |
Beta Was this translation helpful? Give feedback.
-
Hi guys!
Issue: Static Site + Custom Domain Not Working as Expected with AWS Copilot
Problem Description:
I initiated copilot with the command
copilot app init --domain <my domain>
, and my service and environment were created without any issues. When I run the backend service using the Load Balancer Web App, it correctly routes with the URL format<service>.<env>.<app name>.<domain>
, and the routing works perfectly. However, when I deploy the frontend as a Static Site, it generates two URLs for me: the default Cloudfront URL and the automatically generated domain<service>.<env>.<app name>.<domain>
. The issue is that only the Cloudfront route is functional.Steps Taken:
Despite these steps, the issue persists, and I need assistance in resolving this.
Additional Context:
<service>.<env>.<app name>.<domain>
.Any guidance or suggestions on how to fix this would be greatly appreciated. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions