EC2 Instance ssh

I had to set up a security group that gave inbound and outbound TCP access to all IP addresses and attach it to the Internet Gateway. TBH, I googled the answer.

Also, make sure that the permissions on the SSH Certificate that you copy to your local workstation are set to your account only. In Linux, that's chmod 400 keyfile.pem. In Windows, you have to add your user with Full Access and then disable the inheritance to remove the inherited permissions.

I found my mistake so i followed the below steps:-

Download putty and puttygen, or the putty package and install it. Get the .pem file from your AWS EC2 instance. Use puttygen to convert the .pem file so that you'll have a private key --- mistake happened here. I chose "Conversions" tab from PuttyGen, and load my .pem file. After loading pem file, here DO NOT hit "Generate", instead directly "Save private key". That's the key you need. If you click Generate, you'll have a totally different pair of keys. In putty, use ec2-user@your.public.dns.that.you.get.from.aws.ec2.instance, and load the private key at SSH/Auth

Thanks,

I tried that myself, but ultimately had to define an explicit one and assign to the VPC for my instance. Also, for SSH, you will need to have an outbound rule on your default Security Group that explicitly allows connectivity to the Ephemeral Ports (1024-65535), as outbound SSH will connect on one of those ports.

In windows, this is viewable using the netstat command, but in Linux netstat is deprecated in favor of 'ss'. Most distributions still install it with the networking tools, but ss is the preferred command.

I'm having the exact same issue. Not sure why this is happening.