I have created sub domain of my site.
Its on bigrocks.
Now I have ec2 instance with elastic ip and I am running a site from there.
I can access that site by IP/SITE_NAME from local browsers of current machines also. SO it runs on ec2 as well as on current machine.
Now I want to link that site to my su bdomain.
So how can I do that?
I don't want to redirect sub domain.
Browser should display the sub domain name it self and contents from aws ec2 instance
Please help
Login to your cpanel.
go to simple DNS Zone Editor
Enter your sub domain name and IP address of aws ec2 instance in A records and click on Add.
Now you can open your subdomain/site_name and you wil see the page which is hosted on aws ec2 instance.
Create an A record for your subdomain, using the Elastic IP as the value.
Related
Aim: To set-up a subdomain that redirects to an elastic beanstalk instance
I recently bought a domain (tscthub.co.uk) from GoDaddy, transferred it over to 'AWS Route 53' via GANDI, and am waiting on SSL to be approved via 'AWS Certificate Manager'.
Separately I created an 'AWS Elastic Beanstalk' application running Metabase using this guide. This is up and running and I can successfully access it. Whilst the metabase env url works nicely, the public IPv4 address and public IPv4 DNS don't load anything when I follow them.
Next I tried to follow the "Routing traffic to an AWS Elastic Beanstalk environment" guide on the AWS docs. In 'AWS Route 53' I first created a new public hosted zone for 'tscthub.co.uk'. I edited the named servers in the registered domain to match that of the hosted zone. Then because my 'AWS Elastic Beanstalk' environment url had the region within it I thought I could use an alias as per the guide, however, upon trying I got the error "an alias to another record in the same hosted zone are global and available only in US East (N. Virginia)" and unfortunately I'm using 'eu-west-2' (this comment talks about this issue in more detail).
I therefore just used the backfall approach of creating a new CNAME record where the record name was 'test.tscthub.co.uk' and the value was 'http://metabase-env.eba-i2ysq7n4.eu-west-2.elasticbeanstalk.com/'. After waiting a couple of hours for everything to reroute I then tried to access 'http://test.tscthub.co.uk/' but I just get "This site can’t be reached".
It turns out that what the "Routing traffic to an AWS Elastic Beanstalk environment" guide fails to mention is that you can just create an "A" record and set that to the elastic beanstalk environment ...
One of the popular social website accidentally pointed out their domain name to an old AWS EC2 instance IP which was newly regenerated as our instance IP. Because of this when we searched for our product name in google search their website was top listed.
Now this issue has been fixed they are now back to pointing their own EC2 instances but the google search issue remains. This might take some time to get fixed because their's is a high traffic website and ours is just a new launched startup.
How can we prevent somebody else pointing their domain name to our EC2 servers?
I have EC2 instance created in AWS the ip is for example 54.26.12.***
I have my domain (mydomain.com) registered with S3bucket for this EC2 instance, Now this domain shows the index page provided by AWS.
Now 54.26.12.*** is available while hitting mydomain.com in browser.
In this instance, I deployed a war file to tomcat server and I am able to run this as mydomain.com:8080/myAppUrl.
I am looking for show this application url while hitting mydomain.com in browser.
I can put .htaccess file to rewrite urls. But in AWS I cant do that as it is not supported.
How do I rewrite in AWS to my app for my domain.
Update
domain screen now
you could add a A record on your provider (route53, GoDadddy, NameCheap ...) to point myapp.mydomain.com on your ec2 instance.
On the ec2 instance you would need to run apache to listen on port 80 and forward to your app server the requests.
Otherwise you need to change your current A record on domain.com to point to your ec2 IP address and not the S3 bucket
I have a problem where I can't browse a website hosted on an Amazon EC2 IIS instance by domain name. I can browse it by the public elastic IP address I assigned to the instance.
I created a DNS A record pointing a sub domain to the public Elastic IP address. www.whatsmydns.net shows that it is propagated. However, I can't ping my subdomain (ping cannot find the host).
In IIS I created a binding for my subdomain pointing to the private IP address for the elastic IP.
I don't think it matters, but I also created a binding for an empty host name and * for the IP address to be able to connect by the public IP.
I'm completely new to EC2 and thought I wasn't doing something correctly with the elastic IP and/or IIS binding but it's troubling that I can't ping the subdomain. Or, maybe that is expected since I can't browse the site either.
Where have I gone wrong? What should I try/check next?
You can't ping the EC2 instance because by default the security group assigned to your EC2 instance will be blocking ping. To unblock it, modify your security group and add a Custom ICMP Rule to allow Echo Request and Echo Reply.
As for getting your DNS to work within IIS, if I were you to start with, I'd remove all bindings from IIS and then see if you get anything when using your subdomain.
Double check that your subdomain definitely resolves to your elastic IP, you can do this through a command prompt, e.g. nslookup subdomain.domain.com
I got got a new domain that I want to link to aws.
I've already have EC2 instance running.
I'm using Route53 for DNS, and opened 2 records: www.domain.com and domain.com
I updated the register company about the new dns servers from route53.
I do have an elastic IP I linked to my EC2 instance.
the problem is that i can't reach my web site.
I guess I'm missing some parts.
did I miss anything along the way?
EDIT: I can reach my site using the public IP I got from Amazon.
But I can't reach it using my domain.
how can i tell what breaks it?
Some things to check:
Have you definatley set the namservers correctly with the domain registrar?
Have you added the elastic IP address in Route 53?
Some other things that you could possibly check are the firewall settings. This is unlikely the case if you can access the site via the IP address.
Do you know what IP address the domain is resolving to. Is this correct?
Also, you can have look at this blog it will explain lot of things
http://geekospace.com/mapping-aws-ec2-instance-to-your-domain-in-godaddy/