Tl'Dr: I'm unable to (ssh) connect to amazon EC2 instance using private IP.
I'm using private IP because
- Verified that it is
What I'm missing?
The answer to Unable to connect to amazon EC2 instance via PuTTY talked about VPC Configuration, Internet Gateway and NACLs. Do I need to worry about them? As launching Amazon Linux, with everything default is supposed to have everything working out of the box, right?
CodePudding user response：
Ping will not work because icmp is not enabled same as telnet.
- Are you sure your instance is running?
- What command are you using to ssh to the instance can i get the full error it displays.
- I do this on powershell => ssh -i "keypair.pem" [public ipv4 DNS]
CodePudding user response：
The answer to Unable to connect to amazon EC2 instance via PuTTY talked about VPC Configuration, Internet Gateway and NACLs. Do I need to worry about them? As launching Amazon Linux, with everything default is supposed to have everything working out of the box, right?
None of those things you mentioned (VPC Configuration, Internet Gateway, NACLS) exist on the EC2 instance, those are all part of the VPC network infrastructure. Launching a default Amazon Linux EC2 server just means it has some default AWS stuff configured on the virtual machine, it has no bearing on the configuration of the network you are launching it into. So yes, you still need to worry about all those things.
my machine and ec2 are both within my company's VPN & intranet
This is the part I would focus on first. How does your company's VPN and intranet interface with the VPC? How does your company's network know to route the traffic for your EC2 instance's private IP over to the AWS VPC?
Verified that it is appearing under Managed Instances in the Systems Manager console
Then why not use Systems Manager Session Manager instead of SSH? It's more secure.
- Verified that it is