interesting, that should work...
I'll terminate this one and restart a new one all over again.
b.t.w do you know they have limits how many instance you can terminate and
recreates?

thanks!


On Sat, Dec 28, 2013 at 6:26 PM, Chris Miller
<[email protected]>wrote:

> On Dec 28, 2013, at 3:17 PM, ping song <[email protected]> wrote:
>
> thanks pointing me that.
> I registered and tested the whole afternoon...I can never ssh into the
> running server...
> the one that I started is with an IP 54.208.249.155
> but I just can't ssh into it. it looks like a dead one, but the trace
> shows it is alive...
> any advice?
>
> ping@640g-laptop:~/temp-transfer$ sudo tcptraceroute 54.208.249.155 22
> [sudo] password for ping:
> traceroute to 54.208.249.155 (54.208.249.155), 30 hops max, 60 byte packets
>  1  172.25.162.2 (172.25.162.2)  2.308 ms  3.230 ms  3.437 ms
> ...
> 12  205.251.245.121 (205.251.245.121)  61.268 ms 205.251.245.41
> (205.251.245.41)  60.491 ms 72.21.222.87 (72.21.222.87)  61.885 ms
> 13  * * *
> 14  * * *
> 15  * * *
> 16  ec2-54-208-249-155.compute-1.amazonaws.com (54.208.249.155) <rst,ack>
>  51.676 ms  50.564 ms  57.483 ms
>
>
> Your EC2 server should be accessible using a certificate file that was
> issued to you when you created the server. I access my EC2 boxen like so:
>
>     ssh www0.domain.tld
>
> With bits in $HOME/.ssh/config to assist with this:
>
>     Host www0.domain.tld
>         ForwardAgent yes
>         User ubuntu
>         HostName ec2-###-###-###-###.compute-1.amazonaws.com
>         IdentityFile ~/Code/org/key.pem
>
> This is equivalent to the following SSH invocation:
>
>     ssh -i ~/Code/org/key.pem ubuntu@ec2-###-###-###-###.
> compute-1.amazonaws.com
>
> Also, ensure that your EC2’s firewall settings are allowing SSH traffic.
> The allowance of SSH traffic is default for most of the security rules I’ve
> seen, but it doesn’t hurt to double-check.
>
> --
> --
> You received this message because you are subscribed to the Linux Users
> Group.
> To post a message, send email to [email protected]
> To unsubscribe, send email to [email protected]
> For more options, visit our group at
> http://groups.google.com/group/linuxusersgroup
> References can be found at: http://goo.gl/anqri
> Please remember to abide by our list rules (http://tinyurl.com/LUG-Rulesor
> http://cdn.fsdev.net/List-Rules.pdf)
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Linux Users Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
You received this message because you are subscribed to the Linux Users Group.
To post a message, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit our group at 
http://groups.google.com/group/linuxusersgroup
References can be found at: http://goo.gl/anqri
Please remember to abide by our list rules (http://tinyurl.com/LUG-Rules or 
http://cdn.fsdev.net/List-Rules.pdf)

--- 
You received this message because you are subscribed to the Google Groups 
"Linux Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to