1 Answer
- Newest
- Most votes
- Most comments
0
Hello zbdev,
So you have a RDS-database. To run scripts you've set up an EC2 linux instance with a public IP and currently you have problems connecting to that Instance via ssh key from your local computer. But initially you were able to connect and you pushed an ssh-keypair over and after a reconnect it was not possible anymore? Can you explain that? Did you create an additional sshkeypair on your local computer and pushed that to the ec2-instance? Does the connection with the aws-generated keypair work? Things to check:
- Make sure that the securitygroup of your ec2-instance allows inbound ssh-traffic from your ip-address.
- You could try to connect to the ec2-instance via instance-connect in the aws console, for that, make sure that the securitygroup of your ec2-instance allows inbound ssh-traffic from the aws-instance-connect cidrs, see https://github.com/joetek/aws-ip-ranges-json/blob/master/ip-ranges-ec2-instance-connect.json
answered a year ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks for the reply. I added a MyIP inbound rule with my security group and restarted the instance. I tried plugging in the new Public DNS and still couldn't connect to WinSCP or Putty. I tried the "Connect" option on the AWS EC2 Console and that generated this error message "EC2 Instance Connect is unable to connect to your instance. Ensure your instance network settings are configured correctly for EC2 Instance Connect." (Furthermore the help link PDF they provided is broken). Anyways, I'm stumped and don't have a better idea than to start this process over this afternoon. Thanks!
I created a new instance and was able to connect through that. I rebooted the instance this morning and was still able to login. I'm still not sure what happened with the original instance (hence my question), but I've gotten past this issue.