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.
Related
We purchased a domain from GoDaddy, for example, say mycompany.com.
My colleague then moved it to Wix.com to publish our marketing site, which will be available at the mycompany.com url. I need to add a subdomain in AWS, pointing to a Cloudfront CDN endpoint.
To shed more light into the current situation, here is a little more info:
When I check GoDaddy, it shows Nameservers, referencing the Wix servers. For DNS, it says We can't display your DNS information because your Nameservers aren't managed by us.
When I check Wix.com, I see that Managed by Third Party, Connected by DNS and still provides the option to transfer to Wix.
Both Godaddy and Wix provide the option to add a subdomain.
I'd rather do that in AWS.
What is my best option here? Should I transfer the domain to AWS and manage it there? If so, how do I then route traffic from mycompany.com to the marketing site?
Is there a way to keep it as is, but still add a subdomain on the AWS side for example.mycompany.com?
I really regret not registering this domain via AWS in the first place, but lesson learned. Any help would be much appreciated.
I am assuming that your DNS is being hosted via wix.com.
If you want to migrate to Route 53 its not actually too hard. Start by setting up a public hosted zone within Route 53 with the domain name you setup.
Next you would want to perform a zone lookup for all your DNS records, you can use Googles DIG Tool with the ANY option or do this via cli by running dig example.com ANY.
Now that you have all the records you will need to create them within your public hosted zone, follow this tutorial if you need any assistance. Do not add the SOA or NS records.
Now that all records have been migrated get the values from the NS record in your public hosted zone and replace the nameservers within GoDaddy to point at these values.
Your DNS will migrate over whichever period the TTL of your previous NS record is set as. Once this has migrated and it working you can add your CNAME record as you originally wanted to add.
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 have been looking around the internet and I have come across a few different ways to link my AWS EC2 instance to my domain name. It looks like I could do it using Route 53 but I am not entirely sure on that process. The other way is to map it from google. These seem like the best instructions I have found for that: link a Google Domain to Amazon ec2 server
The question that I can not seem to find is what about my email address. I pay google so that I can have some email addresses name#mydomain.com. Now these work fine and I have had them up and running for months. But now I want to have my website (it is a web app) point to it. Because currently when you go to mydomain.com it says This site can’t be reached mydomain.com’s server IP address could not be found.
Some help here on how to do this would be great. I am afraid that I am going to set this up incorrectly and then lose access to my gmail account which I cannot have happen.
Your domain's email is configured via MX DNS records. You would point your domain to your EC2 instance by adding A or CNAME DNS records. The two configurations are completely separate. You will not break your current email setup by adding an A or CNAME record that points to the EC2 instance. You simply need to add that record in your DNS settings, wherever your DNS is currently hosted. You don't need to make any changes in your Gmail account configuration, and you don't really need to use Route53 either (although it does add some nice features). You had to configure the MX records somewhere at some point, to setup your G-Suite account for your domain. You just need to go into that same DNS configuration (most likely still hosted at the company where you initially purchased the domain name) and add an additional record.
I am trying to migrate a PHP site to AWS.
I have created an instance with a specific AWS url and have configured an AWS Route 53 service.
Looking at the docs here: http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html#root-domain-walkthrough-update-ns-record
It says to update the Nameservers for the particular domain, however that would affect the live version of the site which is still being hosted on Digital Ocean.
What I want to do is:
Point a subdomain e.g. dev.mysite.com to the dev environment on AWS
Check everything is ok
Create a live environment on AWS
Point mysite.com to the live environment.
I am still new to this way of hosting, is what I am trying to achieve, feasible.
Or is there another way I should be tackling this.
Any suggestions welcome.
Thanks
That's absolutely fine. Within Route 53, you can create an a record for your Apex (www.site.com) to point to your EC2 (?) instance, and then another CNAME record which points to your dev.site.com
Note that Alias records are free, and the preferred way of doing the above, but only work with certain types of AWS resources such as ELBs.
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.