I am trying to link my godaddy domain with my Elastic Beanstalk app, I did everything in this video http://www.youtube.com/watch?v=NLrE3eGHAR4 although I don't know its right or wrong. I also tried few other things but its not working. Also let me know if there are few other steps that I need to do which are not mentioned in the video.
Thanks in advance
To help you guys more I will add more information,
this is what I did so far,
Associated an Elastic IP address with my running instance.
Created a Hosted Zone and again that created a new Record set for www. and added my Elastic IP address in values.
I updated the NS from the hosted zone into my Nameservers and clicked save.
basically did everything as it was shown in the video.
I know it shows it takes 1 hour to 48 hours to propagate changes over the internet, but it is done maximum within 1 hour if everything is done right.
I hope this information helps.
If you need assign to beanstalk environment custom domain name, you need to create CNAME record in your DNS and point it on elastic beanstalk environment hostname.
Useful reading: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html
Same question here: How to link godaddy domain with AWS Elastic Beanstalk environment?
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?
My first question ever. and newbie to webhosting.
I am trying navicosoft.com vps for the first time for webhosting. VPS just had centOS 7 on it. I installed ruby rails apache passenger etc and deployed my app. App deployed successfully. Here is the IP address http://88.198.121.97/ (site is still in production mode though). I also purchased domain dogtags.pk from http://pknic.net with its nameservers ns1.navicosoft.com | ns2.navicosoft.com. It has been over 72 hours since i registered for the domain.
I want to know what am I doing wrong? why is my site accessible via IP address and not by domain name? If i can get some link to a tutorial or documentation of some kind.
Customer support is very crappy. They are saying we dont provide any technical help for VPS. Help please. Thanks.
EDIT:
The best way might be to use a free DNS service (https://www.google.com/search?q=free+dns+service).
The setup would be as follows:
Use a free DNS service to point your domain name to the correct IP address.
Modify your domain name's nameservers to those of the free DNS service provider you've chosen.
For example, here's a link to how you can set this up with Namecheap's FreeDNS service: https://www.namecheap.com/support/knowledgebase/article.aspx/536/51/how-do-i-set-my-domain-to-use-namecheaps-freedns-service
I recently got an Amazon EC2 micro server to learn how to use nodejs. (I am not servers savvy BTW).
I managed to install everything and having nodejs running on the server and running their example script.
on Amazon I set the server security group to allow all / icmap - all/ tcp - 0-65535/ ssh/HTTP/HTTPS so basically everything is allowed more or less.
My question is how can I find my nameserver so I can use them on a new domain that I've bought.
I might be completely wrong and missing many steps if so. Do you know of a good tutorial on how to do that?
Thanks and sorry for the general question.
I believe what you want to do is point your domain to your new server.
You can do a couple of things in your domain registrar (where you bought your domain)
Add an A PTR record on your domain to point to the IP address of the server.
Add a CNAME record to point to the EC2 DNS name of your instance.
You can find the IP address and EC2 DNS name of your instance on the EC2 console:
You need to setup your domain name on Amazon's Route 53 DNS service in order to use their nameservers. Check out the link on how to retrieve the nameservers: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html
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/