#✅ - Permanent Amplify Custom Endpoint set up

9 messages · Page 1 of 1 (latest)

glacial mantle
#

Hello all,
My Amplify deployment has been successful, and it's connected to my Git repository, working great on the default domain.

However, setting up my custom domain has been tricky. I've double-checked multiple times to ensure all the required DNS records from Amplify are correctly added to my domain settings right after adding the domain, but no matter what I do, it remains stuck on this status. I've also tried deleting and re-adding it, but I'm feeling stuck. I've just been adding the records that are in the View DNS Records part in the domain page for Amplify. I have used DNSChecker and it seems to be properly pointed so I don't think it is causing the issue.

Additionally, I saw 4 name servers listed in Route 53 for my domain. I'm not sure if I need to add those to the DNS records,and Squarespace won't let me if we need to add them to our domain's DNS records.

Could anyone point me in the right direction? Any advice would be greatly appreciated!

harsh aspen
#

Hey @glacial mantle , the root cause is likely related to how the Route 53 hosted zone is setup with your domain registrar (Squarespace). Since you have a Route 53 hosted zone, I am assuming you want to use it as the primary DNS service. I'd recommend reviewing this Route 53 guide to ensure you have the correct NS records included in Squarespace's DNS settings: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html#migrate-dns-change-name-servers-with-provider

glacial mantle
#

Is there a way to do it without Route 53? I don't want to use it.

harsh aspen
split spruceBOT
#

✅ - Permanent Amplify Custom Endpoint set up

split spruceBOT
harsh aspen
#

cc @glacial mantle

glacial mantle
#

d2m5wa0fh4dlfc

glacial mantle
#

?