amazon web services - Why does SSH timeout when connecting to a load balanced elastic beanstalk instance -
i've created single instances in past , familiar process:
create keypair use keypair when setting instance ssh using "ssh -i path/to/key.pem ec2-user@xxxx.elasticbeanstalk.com"this when seek connect using "-vvv"
openssh_6.0p1 debian-3ubuntu1.2, openssl 1.0.1c 10 may 2012
debug1: reading configuration info /home/tha_user/.ssh/config
debug1: reading configuration info /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: applying options *
debug2: ssh_connect: needpriv 0
debug1: connecting xxxxxx.elasticbeanstalk.com [23.23.182.171] port 22.
debug1: connect address 23.23.182.171 port 22: connection timed out
ssh: connect host xxxxx.elasticbeanstalk.com port 22: connection timed out
the timeout seems firewall rule somewhere blocking me, keypair has inbound rule of "accept tcp port 22 anywhere." there else in aws scheme might blocking me? i'm still quite new aws , it's various systems , rules.
are sure using right ip address ec2 instance, , not "elastic beanstalk" ip address? not believe ec2 instances in beanstalk have public dns, ip address. fact have elasticbeanstalk.com in ssh command makes me think doing wrong.
to ssh ec2 instance, need find instances in ec2 console. public ip address, , seek ssh instead of beanstalk.com dns.
i create pem file each of beanstalkers, , way can tell ec2 instances part of beanstalk pems.
amazon-web-services ssh amazon-ec2
No comments:
Post a Comment