I have followed what the guideline(https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Internet_Gateway.html) has told me to do, and my instance have an Elastic IP. However, when I paste the Elastic IP into my browsers(Google Chrome/ Microsoft Edge) none of them worked. Here is a screenshot of the Security groups.
Any help is appreciated!
update 1: Sorry I am new to stackoverflow and forgot to post the screenshot last time. Now you can view the picture.
update 2: I think I've connected my instance with the Elastic IP. See here
update 3: Thanks everyone who offered help. I think I've made it. It is actually something about the firewall :-)
Related
I have a site hosted on AWS EC2 instance. I stopped the instance and started it up again and noticed the IP address had changed. Due to complications with this happening posts I read online suggested using an elastic IP. I allocated one and associated it with my EC2 instance. I also made sure that my hosted zone is pointing to my elastic IP. Now when I try to go to my domain I get the error "[site] refused to connect". I am able to ssh into my instance via terminal using the elastic IP. I am lost on where to go next. Any advice would be greatly appreciated. Thank you in advance!
Thanks to #strongjz I have the answer to the question. Hopefully this will help someone else in the future. Once you stop an amazon EC2 instance, not only do you need to check your IP address as it will change but also make sure to ssh into your instance and run sudo service httpd start to make sure that your web server is running. This was the problem for me. Took me days to figure it out. Big thanks to #strongjz for helping me with this!
HI I notice that on some spot instances I get this weird issue whereby the instance does not have any network options nor can I associate an IP with it. I checked and its all running from the same data centers (us-west-1a) sometimes it works and sometimes it does not. Has anyone else experience this or have an idea what I can do? thanks. Below is an screenshot.
Most likely you have more than one instance selected. In that case some of them (including Networking and Instance Settings) are greyed out.
Select just one instance and try.
Thanks to #Michael-sqlbot in comment above the issue was when creating a spot instance there is an option under network to either select ecs-classic or VPC. A bit of confusion is that only certain ecs type of an option to chose while some just default to VPC. This was why sometimes some of spinups has network options like elastic IP, etc. Anyways, by manually chosing VPC I'm now able to configure the network now. thanks.
I recently set up a new site on AWS EC2 instance. It works fine from the office, but when I go to the site from my phone it hangs and then times out. I'm new to AWS, so maybe I missed something during the setup. It's a basic lamp stack. Nothing in the logs. I don't think requests are even getting to the server. Any suggestions appreciated.
Thanks.
The issue from your question and comments is that you do not have http port 80 open to public. Please add below rule to your EC2 security group and your website will work everywhere.
I have a domain name registered with Hover.com and I'd like to use it to point to an Amazon EC2 Instance. I can't seem to figure out the proper way to do this, despite my Google-fu. If anyone has had some experience with using these two services together, some advice would be much appreciated. Thanks!
There are a few ways to do this, the simplest is pointing the domains A record to an IP address that is associated with an instance. So:
Go to EC2 dashboard
Create an Elastic IP
Point the A record to this Elastic IP
Associate the Elastic IP to an instance.
This link http://aws.amazon.com/articles/1346 should help although it is using the command line tools. The steps above are for the GUI.
The other method is to use Route 53 - this guide helped me out http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/R53Example.html
i've registered a .com domain name. At the Amazon Web Services account i own, I have already set up the DNS zone,i've changed the nameservers at my registrar's panel and i've created an A-record in my AWS DNS zone,too. I think i've done all the preparation needed. But my website is not opening!
This is not a DNS propagation time-requiring issue,by the time i did all the above stuff about 5 days ago (DNS had enough time to be refreshed globally in any ISP). Also via ipduh.com i can see that all the nameservers are correctly configured and recognised, as well as the *.mydomain.com A record which points at my AWS instance's IP.
What possibly would be wrong guys? :/ i've done anything i know and i've followed also the directions i've found in SO and i had no luck till now :/
Any suggestion and help would be highly appreciated :D
Thank you in advance guys!
I'm going to assume that the DNS is set up properly, and that the A record is pointing at the IP address assigned to your instance.
If this is a new AWS account, you're probably running in a VPC. Did you make sure that you allocated a public IP address to the instance? If your IP is 10.something, that's the internal, private IP address and you won't be able to use that. You'll need to allocate an Elastic IP and associate it with your instance, then update your DNS settings.
Next, make sure that the web server is up & running? If you log into the instance, what happens if you wget localhost? You might not get the page you're expecting if you're running multiple name-based virtualhosts, but you should get the index page for the default web site.
OK, so how you're sure the web server is running. Next thing to do is check the security rules. When you created your instance, you had give it the name of a security group. The default is, strangely enough, called "defaut". Take a look and see if port 80 is open. If not, open it up to the world (0.0.0.0) and see if you can access the web site now.
None of this helps? Reboot your instance and see if it starts working when it comes back up - it's possible that you're on a bad host, and rebooting will bring it up on different hardware.