#✅ - Subdomain setup not working - wrong CNAME?

6 messages · Page 1 of 1 (latest)

dusty sparrow
#

I've followed the instructions here for adding a subdomain and it's now been over 48 hours but am still unable to reach my amplify app at the subdomain.
https://docs.aws.amazon.com/amplify/latest/userguide/to-manage-subdomains.html

When I check https://www.whatsmydns.net/#CNAME/beta.syncmyworkout.com it shows that the CNAME has propagated across global nameservers, so I'm not sure what the issue is.

I'm a little confused by these instructions, they seem to contradict each other. When I try visiting my <id>.cloudfront.net url directly it 404s.

Found under Amplify -> App Settings -> Domain Management -> Actions -> View DNS Records

If you are migrating a custom domain that is already serving production traffic, please wait until your new application loads successfully at the <id>.cloudfront.net url shown below before updating your DNS records:

Found under: https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html

I get a 404 error on the CloudFront URL
To serve traffic, Amplify Hosting points to a CloudFront URL via a CNAME record. In the process of connecting an app to a custom domain, the Amplify console displays the CloudFront URL for the app. However, you cannot access your application directly using this CloudFront URL. It returns a 404 error. Your application resolves only using the Amplify app URL (for example, https://main.d5udybEXAMPLE.amplifyapp.com, or your custom domain (for example www.example.com).

Should I point the CNAME to my prod.du0vcipq8yvcf.amplifyapp.com instead?

#

Subdomain setup not working - wrong CNAME?

dusty sparrow
#

Ok I figured things out 🙂 the docs need to be updated though. See github issue for resolution.

errant groveBOT
#

✅ - Subdomain setup not working - wrong CNAME?