Sounds like you have everything set right in the security group. Have you checked that the webserver is actually listening on external interfaces :)? I for one often forget about the default bind interface/address...
On Sun, Aug 14, 2011 at 10:05 PM, Kevin LaTona <[email protected]> wrote: > I tried the default group and no luck. > > So I made a "web" set which is nothing more than port 80 set at 0.0.0.0/0 > for TCP calls > > Being setup this way I thought it would allow any and all incoming IP > addresses through. > > I have the same settings for SSH on port 22 and it's coming through. > > Like I said I have to be missing something simple. > > Thanks > > -Kevin > > > > > On Aug 14, 2011, at 9:50 PM, Dave Parsons wrote: > >> AWS has their own security settings for allowing ports through to your EC2 >> instance. In the EC2 tab, look at the Security Groups tab. Click on the >> group you are using (probably "default"), and then the "Inboard" tab. Open >> up port 80 and probably 443. I spent a few hours on the same problem many >> months ago. >> >> Dave >> >> >> On Sun, Aug 14, 2011 at 9:44 PM, Kevin LaTona <[email protected]> >> wrote: >> Hi All, >> >> Anyone on the list have AWS EC2 firewall rules down pretty good and might >> be able to lend a thougth? >> >> Seems no matter how I set the firewall rules. >> >> I can't get my web server talking to the outside world. >> >> I can SSH in okay. >> >> I can run the same webserver set on a local Ubuntu box just fine. >> >> It's probably something simple that I am doing wrong. >> >> Thanks >> >> -Kevin >> > >
