I bought a domain (let's say example.com) from google domains a couple of days back, but found out their web hosting is terrible. They only allow me use one of their partner hosting services. I want a simple ssh/ftp based web hosting service, where I can simply dump the html files.
So, I turned to AWS webservices to host my website. Everything works well, until I want to assign it a domain name. AWS assigned me a domain like "mytest-bucket.com.s3-website-us-west-2.amazonaws.com/", but I want to use my bought domain.
AWS allows me to buy a new domain from it, but I already have one (example.com), and want to make AWS host my website under that domain name.
Apologies if this is a newbie mistake/question but I am new to commercial web-hosting.
There is a option in AWS Route53 where you can transfer domain to AWS. Check this guide.
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.html
Another way is you can change the DNS servers to Route53. Check this guide.
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html
Another option is you can add "mytest-bucket.com.s3-website-us-west-2.amazonaws.com" as a C-name to your domain in Google and your domain "example.com" will start showing the website.
Related
website 1 hosted on namecheap with a domain www.domainname.org also bought from namecheap. I want website 2 which is hosted on aws to have domain name shop.domainname.org
i know how to connect a third party domain name to Route53 on aws and setup subdomains but i want to be sure that if I do that through the normal custom dns on namecheap website 1 would not be affected, or better still if there is anyone with experience on this please give me a step-by-step guide
You just need additional A record on Name cheap. They have it documented very well https://www.namecheap.com/support/knowledgebase/article.aspx/9776/2237/how-to-create-a-subdomain-for-my-domain/
I have a domain hosted through Google. I'm using Google Workspace for a lot of my day-to-day operations (e.g. Drive, Gmail, etc). I'm using AWS as my infrastructure and business logic for my application. I'm having trouble making my site support TLS. If you visit it now, you get this on chrome and I can't seem to make HTTPS requests work.
I have my domain pointing to AWS via Custom Name Server.
My route 53 has the NS type records listed under the hosted zone
I've tried to request a Certificate from AWS to make it work.
My problem is I don't know how to tell Google about it. How do you let Google know about the certificate so I can make my site HTTPS?
I believe approaching Google is not going to solve your issue as in the above case Google is only responsible to host your domain . So DNS setup is only responsible to route requests to your site and not making your site more secured.
I also found that you are exposing your site as http rather than https and thats why your site is unsecured.
Is your site is running on a web server or is it hosted on S3 as static web site ?
Note: you cant enable https on S3 static website.
The workaround to above problem is below :
Route53 has A record to pointing to ALB (configured with ACM) distributing traffic to Ec2 instances running your web application.
If anyone is still looking. I wanted to keep it cheap with a simple S3 static website. If you want to maintain the S3 part, make a CloudFront distribution (if you haven't already.
Inside the CloudFront under the main settings, use a Certificate you made from Certificate Manager.
Then head over to Route53 (even if the domain is hosted via Google) and route the "A" name record to the CloudFront. NOTE: make sure the "Alternate Domain" name is filled in or else it won't see it.
Let it update for about a minute or two and it will show https
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've recently converted from using traditional registrars and started using Google for website hosting and domain registration. I've followed various guides and am currently infuriated at how hard it is to connect my domain owned by google to the google cloud instance while retaining email forwarding.
In order to point the domain to my VM in requires changing the nameservers. Once the name servers are changed then email forwarding stops working. I'm stuck in an infuriating loop. There has to be a better way.
Here's the process I followed
Google Domain > ExampleSite.com
Google Domain > support#examplesite.com (email forwarding to default gmail account)
Google Cloud > Create Wordpress VM instance
Google Cloud > Add DNS Records
Google Domains > Update Nameservers with info from Google Cloud DNS
Works, but email forwarding is immediately disabled unless I revert to default google nameservers, which stops the domain from pointing to the VM.
Please. Anyone. Help with a better way of doing this. Please. I'm so frustrated.
Thank you.
The reason why email forwarding breaks that your Cloud DNS is not configured with the necessary MX records. Here are the two possible solutions:
Add the MX records described here to your Cloud DNS configuration.
Revert back to Google Domain's name servers, which has the MX records built in. You can then set up your website by creating an A Record for the # record and www subdomain record to point to your GCE's IP address.
If all you want to do is to host a website I recommend (2), as it saves you the cost and complexity of having Cloud DNS as well as Google Domains.
So, this is my first time setting up a simple website and I decided to purchase a domain on Google Domains and I plan on hosting it on the AWS Free Tier plan. The domain was purchased last week. So, I am cannot transfer because the domain name is within 60 days of initial registration.
The goal is to create a simple landing page which uses a PHP script to generate a simple mailing list.
I have read this link 2-3 times already and followed all the steps:
https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html
I want to keep all my G Suite features but I cannot because the guide asks me to copy AWS nameservers in my hosted zone to the DNS settings on Google Domains. This results in this.
I want to stick to AWS and not move to another hosting service, for certain reasons. Please guide me in the right direction. Thank you.
So I was able to fix this after I studied a bit and posted it on Reddit and got the answer.
Because we are working with subdomains, I made an S3 bucket with the subdomain name. I made the files public and generated the standard policy. Took the S3 bucket endpoint, and then went back to Google Domain's DNS settings.
I didn't need Route 53 in the first place. All I did was create a CNAME record with the subdomain and set TTL to 1 minute and the S3 endpoint as the data. And BOOM! It worked.
I believe when I move on to create more dynamic websites, I have to expand my search and learn more.
Thank you for everyone's help.
You can keep using Google Nameservers, along with hosting your website on you AWS Server (whatever the service you are using, like EC2, beanstalk).
Suppose if you are using an EC2 instance to host your server, make a note of its Public IP (I'd recommend using elastic IP). Now go to your google domain record set and create an A record with the IP of your EC2 instance.
refer https://support.google.com/a/answer/2579934?hl=en for details.
Using route53 is optional. It just helps you to store resource records. If you can create them somewhere else, Route53 is not required.