Amazon EC2 – How to Access Public DNS

amazon ec2amazon-web-services

I'm working with Amazon's EC2 for the first time.

I went through all of the steps at http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/ and now I'm trying to access the public DNS through a web browser. I get nothing. I don't even know if I'm supposed to get anything, really.

I just want to see something that indicates that my instance is accessible from the web for development's sake. I'm completely new at this and I can't find a simple answer to this anywhere to save my life.

Any help would be MUCH appreciated. Thanks!

Best Answer

The default is not allowed any connection to the instance. The same can not be installed Web server.

allow ssh(for UNIX) or RDP(for Windows) and HTTP
- open https://console.aws.amazon.com/ec2/
- NETWORKING & SECURITY->Security Groups
- select default
- add rules to SSH(for your ip or 0.0.0.0/0)
- add rules to HTTP
connect to the instance and install Web server
check public DNS through a web browser

Related Solutions

Ubuntu – Why does the EC2 nameserver (correctly) resolve names to private IPs and then switches to public IPs

options {
    forward only;
    ...

From BIND ARM97:

forward This option is only meaningful if the forwarders list is not empty. A value of first, the default, causes the server to query the forwarders ﬁrst — and if that doesn’t answer the question, the server will then look for the answer itself. If only is speciﬁed, the server will only query the forwarders.

In your case, as you actually need amazon DNS servers for .amazonaws.com only, you may also do:

options {
    forwarders { };
...
}

zone "amazonaws.com" {
    type forward;
    forwarders { 172.16.0.23; };
    forward only;
};

Can’t Start 64-bit AMI on t1.micro instance on AWS

Your ami-c0b368a9 is 32-bit.

For some reason, it was registered with a 64-bit kernel image (aki-825ea7eb).

Your AMI and AKI need to match in architecture.

You could simply specify a 32-bit kernel to run with the 32-bit AMI, but it's probably best to build and register the AMI correctly.

Best Answer

Related Solutions

Ubuntu – Why does the EC2 nameserver (correctly) resolve names to private IPs and then switches to public IPs

Can’t Start 64-bit AMI on t1.micro instance on AWS

Related Topic