I am attempting to set up a new website in AWS Lightsail and am unable to get my domain to point to my Lightsail instance. The domain was purchased in Route 53, and in that domain's hosted zone I have set up an A record to point to my instance's static IP. When I navigate to that static IP directly, I can access the site without issue.
These issues began occurring after attempting to create an SSL certificate in the Lightsail distribution tools. After configuring the distribution and DNS Zone, I edited the name servers in both the domain registry as well as the hosted zone in Route 53 to match what is recommended by AWS under the Lightsail DNS Zone information. It has been over two days since these name servers were changed, and I still cannot navigate to my instance through this domain.
Any suggestions even for how to troubleshoot this issue would be very much appreciated. Has anyone run into similar issues with Lightsail and Route 53?
Related
I have a marketing website on wix with domain registered with godaddy, I've added a subdomain pointing to my EC2 IP for my app facing server, which works fine. Now I want to add a load balancer in front of that EC2 instance, however I cannot set the ELB A record in GoDaddy. Following this answer I created a hosted zone but if I change the name server I'll loose access to my wix website.
I want only the subdomain to point to my ELB while the main domain continues to point to the wix website, - do I need to change the name servers in GD to point to the aws hosted zone and then in the hosted zone map my main domain to the wix website and the subdomain to the elb? Do I need to move my domain registration to route 53 altogether?
What is the most recommended setup for this scenario?
Figured it out, writing for future help.
You need a hosted zone on route 53 pointing to the ELB, this gives you name servers. In GoDaddy add those name servers with your subdomain, keeping the existing name servers intact :)
I have a simple AWS setup of 2 VMs hosting a WebApp. An Application Load Balancer is in-front of these machines. I can access the DNS name of the Load Balancer and can reach to the WebApp.
Now, I want to connect to my app with a domain name hosted on Godaddy. I tried to simply create CNAME (as no Elastic IP on Application LB) with the LB's DNS name, but it didn't work.
What am I missing ? I tried with godaddy support but already wasted 7 days with not solution.
I want to put SSL certificate also on ALB. Should I be aware of anything specific in this setup?
The problem was, I was trying to CNAME for root level domain. Now, I created an alias in Route 53 and used AWS's nameservers on Godaddy to forward request there.
I have a Wordpress website with a GoDaddy domain being hosted on SiteGround using the nameservers. I am looking to switch to a React App which is currently running on an EC2 instance in AWS. I want to run the ec2 instance (aka the react app) on a subdomain like beta.domain.com inside SiteGround while still keeping the Wordpress website since its a part of my business. I tried creating a subdomain in SiteGround and then pointed it to my EC2 instance elastic IP (the public ipv4) using an A record but it is showing "This site can't be reached" error once I go to beta.domain.com.
What am I doing wrong? How do I run the EC2 instance in a subdomain hosted in SiteGround?
EDIT
Thank you, everyone, for your help. The problem was the SSL certificate for the HTTPS. The website wasn't coming on due to the HTTPS setup on the Nginx on the EC2 instance. After I put in the details of the certificate it runs properly with just the A record.
Any public address in the AWS environment are never accessible from outside the security groups. Even if you try to ssh from your own machine and if it is not in the inbound rule of the security group of your EC2 instance. I feel there are 3 ways out here.
1.) Adding an all traffic rule in your EC2 Security group inbound rule. This is not recommended as it opens all traffic to your machine.(additional tip: set up secure ssh key with the machine)
2.) Use an ELB to route traffic to your EC2 instance. ELB will provide you with a DNS record which can be used an a CNAME in godaddy(Point 3 shows how to map it as a A record in GoDaddy)
3.) Using Route 53 Hosted Zones - You could delegate your DNS to be managed by AWS Route 53. This way all traffic will be routed to your machine by AWS R53.
Another tip: Elastic IP can also be used which are like permanent static IP Addresses accessible from across internet. This provided a secure communication method to your instances.
Let me know what could be the favorable solution for you. I could help you out further
If you have registered your domain name with Goaddy, you can create subdomain in Godaddy as CNAME and point it to static IP address of your ec2 instance. Here is a link to guide you.
Also your main domain name will point to your Wordpress website on SiteGround.
Now that you have EC2 instance, you can also run a wordpress site on that instance if you like.
I have a domain name registered with tmdhosting.com. And I have created a WordPress multisite setup on AWS using bitnami WordPress multisite stack.
Now I would like to point my domain name from my registrar to my AWS instance. Where they are asking me to provide them with a NS. I am new to AWS and I am not sure as to how to go about doing this.
Also did a little bit of research where it said that I will need a Route 53 (which is not free) I would want to know if there is another way to do this.
Can I use CloudFront to do this as with my previous provider had given me a cloudflare name server.
Please let me know the steps as to how to go about doing this.
To point a Domain Name to an EC2 instance, you can either use Route 53 or your own DNS service. In both cases:
Assign an Elastic IP address to your EC2 instance
In Route 53 or your own DNS service, define a domain/subdomain that points to this IP address
The above assumes that you wish to point to a single EC2 instance. If you have multiple instances with a Load Balancer in front, you will require a CNAME record pointing to the DNS name of the Load Balancer. (If using Route 53, using the "ALIAS" button to point to a Load Balancer.)
Route 53 is not free, but it is very cheap. If correctly configured to point to AWS resources, it can cost only 50c/month per hosted zone.
CloudFront is a content distribution network that caches web content. It will not assist you in assigning a Domain Name to an EC2 instance. (Custom domain names can be used with CloudFront, but that doesn't appear to be your particular question.)
I have a domain registered with namecheap and its DNS records are managed by AWS Route 53. Currently the domain points to a regular EC2 instance. I'd like to get a subdomain set up pointing to a separate EC2 instance (specifically, an Elastic Beanstalk instance). I've got the Beanstalk instance set up (so if I visit the elastic IP for that instance, everything works fine).
THe problem is, all the docs I've seen on adding a subdomain to Route 53 imply that the parent domain's DNS records are still managed by the registrar. I'm unclear as to where I need to add the new NS records for the subdomain in order to have it point to the right thing.
Here is an example of a domain hosted at namecheap.com, DNS handled by route 53, website hosted on aws ec2 instance and the email server is hosted at Rackspace email.
Your situation is pretty close to this, so you should be able to follow this example and change to your specifics: