I have created an EC2 instance that host a wordpress site.
Then I have created AMI image with it and created exact copy of the instance.
The instance that I have copied from is linked to a domain through Route 53.
A bizarre experience that I have right now is that (twice now), when I copy EC2 instances in a way described above, using HTTP to access either of the EC2 instances lead to re-routing to the domain that was routed by Route 53 for the first instance.
Shouldn't only the first instance be linked to the domain because that is how I have set the record in Route 53? Is it normal for duplicated EC2 instance to point to same domain when I copy it using AMI image? How do I make it so that the second copied instance does not get re-routed to the same domain as the first instance?
This really is unrelated to AWS, EC2, Route53, etc. You simply have the "Site Address" setting in your Wordpress configuration set as that specific domain name. Wordpress automatically redirects any incoming requests to the configured Site Address.
Related
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 hosted on bigrock.in pointed to an Amazon EC2 instance using Route 53. The four nameservers generated are placed in bigrock and it is working fine.
Now I have created a subdomain of the domain in bigrock and I want it to point to my application in another EC2 instance in another AWS account. Is this possible?
Yes. The AWS account that is currently controlling your domain name with Route 53 must be used, but it can be pointed to anything on the Internet.
Steps:
In the AWS account with the "other" EC2 instance, create an Elastic IP Address and assign it to the EC2 instance. This will ensure that its IP address does not change when the instance is stopped and started.
In your existing Route 53 configuration (in the original account), create a Record Set for the sub-domain (eg images.example.com) of type A and enter the Elastic IP Address as the value.
Once you have set the nameserver for your domain to point to Route53, you no longer need to control the subdomains from bigrock services. Just add them to your Route53 dashboard, and they'll be reflected live.
I have a root domain like example.com. It's now hosted on Amazon S3. For that I followed this tutorial:
http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html
What would I have to do to have a subdomain like client.example.com to point to a EC2 instance?
client.example.com => ec2-XXX.us-west-2.compute.amazonaws.com
Is there like a tutorial out there explaining the steps?
Two simple steps:
You would just need to add a new 'A' record to assign the ec2 ip address to that subdomain in your amazon route 53 dns (or whatever dns provider you are using) - very simple to do. Step one will have requests for that sub-domain routed to the ec2 instance.
Step 2 is to tell the web server you are running, when it receives a requests for that sub-domaain, what website should it serve up to the user - you do this by 'binding' the name to the directory/location thast has the website on your ec2 instance.
You may also want to read over the following from AWS
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-ec2-instance.html
It would also be better practice to assign your EC2 instance an Elastic IP address then forward requests to that IP.
We recommend that you also create an Elastic IP address and associate
it with your Amazon EC2 instance. An Elastic IP address ensures that
the IP address of your Amazon EC2 instance will never change.
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 the instance ec2-xx-xxx-xxx-xxx.ap-southeast-1.compute.amazonaws.com. It is running a bitnami lamp stack.
How do I create a subdomain for this like subDomain.ec2-xx-xxx-xxx-xxx.ap-southeast-1.compute.amazonaws.com?
Is it possible to do such this or should I purchase a domain first?
Thanks
You cannot manage AWS domains. You need to have your own domain first and use Route 53 or any other DNS provider to create an A record pointing to this specific EC2 instance.
Before creating the A record however you will need to provision an Elastic IP and assign it to your EC2. Please keep in mind that every account starts out with only 5 Elastic IPs and if you need more you will have to get in touch with Amazon for approval.