I'm trying to host a custom domain name using Amplify & Namecheap. It hosts the website for a day or so, and then it says "the domain association has failed because we couldnt find the correct CNAME records."
This is currently what my amplify console looks like.
Amplify Console Message
This is what my namecheap DNS settings currently are.
This is what the DNS propagation comes up as
Help would be greatly appreciated!
Related
can someone help me with this problem. I believe I am using the correct DNS record; ANAME(Alias record) for this but it is not working. I am using a third party domain name management instead of using the inhouse DNS 53 from AWS. I created a react application using amplify from aws but I am not able to point a record from my DNS. I have successfully added the DNS record(as you can see in the photo) but when I go to the record site it gives me the error below.
Thank you!!
enter image description here
enter image description here
You can follow some steps to achieve this :
Once you set up AWS Amplify
For Host, enter only the subdomain. For example, if your subdomain is www.example.com, enter www for Host.
For Points to, look at your DNS records in the Amplify Console and then enter the value. If the Amplify Console displays the domain for your app as xxxxxxxxxxxxxx.cloudfront.net, enter xxxxxxxxxxxxxx.cloudfront.net for Points to.
I think one correction you have to do is instead of amplify endpoint you have to get cloudfront endpoint as per step 3.
More details can find here : https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html
I´m probably not understanding something here and wanted to ask, if somebody could explain.
I set up an AWS ES domain and created a custom endpoint for it. I provided a ACM certificate which I uploaded upfront and created the domain with it.
Let´s say, the custom endpoint should be a subdomain of my existing ROUTE 53 Domain (eg. logging.my-r53-hosted.domain)
I didn´t do anything at Route 53, yet, just provide an imaginary subdomain as endpoint(example above).
Then what ? .....
When I create this subdomain on Route 53 as CNAME which points to the autocreated endpoint of AWS ES (eg. vpc-logging-72354762589234579.es.amazonaws.com) and curl the custom endpoint (logging.my-r53-hosted.domain) I´m getting just the aws certificate back, but not the one i provided before. That gives me a self signed cert warning. I can circumvent this with --insecure, but that´s obviously not what I want.
Can anybody explain how to do it right ?
Thanks all and again thanks for your patience :-)
Greetings!
Create a wild card certificate like *.youdomain.com in ACM.
While creating the ES cluster select the custom domain option and add Custom hostname as your subdomain (e.g: elasticsearch.yourdomain.com) And for certificate chose wildcard certificate from ACM.
If you have cogito auth for kibana You will need also need to follow these steps:
Go to Cognito pool
Under App integration > App client settings
Update Sign-in and sign-out URLs according to your subdomain.
I have an issue, or perhaps an understanding problem with linking my domain with AWS. I will use the xy.ro domain as an example.
I have the xy.ro domain registered with easyhost.com. On AWS I have a node.js express web app.
My xy.ro domain is not working as it does not point to anything.
I tried to create a hosted zone on AWS with the xy.ro domain and tried to create a dataset for this domain but it does not work.
I tried to find step by step instructions also on AWS and other providers but I did not find anything.
Can someone point me into the right direction?
If your domain xy.ro is registered with easyhost.com then it would presumably also be using their DNS hosting service to serve your DNS records.
Creating a public hosted zone in AWS won't affect the DNS resolution unless you can migrate your name servers to use Route 53.
I was not able to see steps from easyhost.com website, however from the AWS side take a look at this documentation.
You should be able to copy the name servers and update within easyhost so that it will use Route 53 as your DNS provider instead.
I am trying to verify my website on google console and it is asking me to add the verification code into dns configurations. I purchased the domain from godaddy and hosting my website on aws server that's why godaddy's dns configuration has name servers provided by aws.
Now when I am trying edit the records of my domain in Godaddy.
It says:
We can't display your DNS information because your nameservers aren't managed by us.
Which is because I am not using Godaddy's nameservers.
I wanted to know which is the right place to add the googe verifcation code is it godaddy or aws?
If it is AWS where should I add the record.
Open AWS Route53
Create Hosted Zone if you are not created.
If already created then create record set
Select TXT record and add your value.
I am developing Mycroft Nutrition and am attempting to switch my domain from pointing at Heroku to an AWS endpoint because I just switched to AWS Lambda for a serverless architecture. My new endpoint is https://usfqa3q0sg.execute-api.us-east-1.amazonaws.com/dev/, which is working fine, and I have set my DNS accordingly:
However, mycroftnutrition.com still is not working. Can anyone point me in the right direction to getting my domain working?
Update
I created a custom domain for my API as per #matt-healy's recommendation and now have this:
I set my DNS to be this but still have no luck:
You've set your DNS entry to point to:
usfqa3q0sg.execute-api.us-east-1.amazonaws.com/dev
which is not a valid domain.
What you want to do is set up a Custom Domain Name in API Gateway which will map the domain name address to the "dev" stage of your API endpoint.
For more information you can view the documentation.