Skip to content

EC2 Instance Connect does not connect to public IP but to private

0

Hi, Trying to Connect using EC2 Instance Connect. It supposed to "Connect using the EC2 Instance Connect browser-based client, with a public IPv4 address" but instead it connects to private IP. Also, RDP can't connect to instance. Something changed/broken. Any tips how to fix it? Thank you, Alex

asked a year ago273 views
1 Answer
1
Accepted Answer

I think you are thinking about it connecting via Private IP when you use an EC2 Instnce Connect Endpoint.

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/connect-with-ec2-instance-connect-endpoint.html

Here are the specific directions to setup RDP to your Windows instance.
Connect to your Windows instance

Hope this helps!

AWS
EXPERT
answered a year ago
EXPERT
reviewed a year ago
EXPERT
reviewed a year ago
  • Thank you, iBehr, I use: Connection Type option "Connect using EC2 Instance Connect Connect using the EC2 Instance Connect browser-based client, with a public IPv4 address."

    Not this option: "Connect using EC2 Instance Connect Endpoint Connect using the EC2 Instance Connect browser-based client, with a private IPv4 address and a VPC endpoint."

    But it connect to private IP that is Endpoint. This make RDP to fail. RDP worked fine before EC2 Connect could connect via public IP.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.