[cs615asa] Fwd: (no subject)
batkinso at stevens.edu
Tue Feb 14 13:29:01 EST 2017
Again, not really sure why but everything seems to be working okay now. I
was messing around with it last night but when I went to sleep I was still
unable to connect. This morning I got it on my first try with the same
commands (I copy and pasted, so I'm sure they're the same). I'm still
stumped, but at least everything seems to be working. I'll still post the
commands just in case there's something obviously wrong that's causing it
to sometimes work and sometimes not.
aws ec2 run-instances --image-id ami-1a60f82a --count 1 --instance-type
t1.micro --security-group-ids devenv-sg --key-name devenv-key
aws ec2 describe-instances --instance-ids i-0fae36915f471378f --query
ssh -i devenv-key.pem ec2-user at 126.96.36.199
aws ec2 describe-security-groups returns:
SECURITYGROUPS default VPC security group sg-6703811f default
USERIDGROUPPAIRS sg-6703811f 120119680155
SECURITYGROUPS security group for dev env sg-f501838d devenv-sg
IPPERMISSIONS 22 tcp 22
On Tue, Feb 14, 2017 at 12:47 PM, Jan Schaumann <jschauma at stevens.edu>
> Bryana Atkinson <batkinso at stevens.edu> wrote:
> > I've been completely unable to ssh into any instances for a couple of
> > days now.
> If you keep getting "connection timed out" even if the 'aws ec2
> describe-instances' command shows them as running, then this would
> suggest that the network connections are not allowed, possibly because
> your security group settings do not permit ssh from the system from
> which you're connecting.
> How did you create the instances? Show us the exact commands as well as
> the output of 'aws ec2 describe-security-groups'.
> cs615asa mailing list
> cs615asa at lists.stevens.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cs615asa