Remote Desktop to EC2 instances stopped working
Apologies if the question is too simple. As soon as I created a second EC2 instance - lost the ability to RDP to the first instance and was unable to RDP to the newly created one. Any ideas? No security settings were updated. The security group is set to "Default" and allows all inbound/outbound traffic. There's a message that's displayed when you go to the "Connect" settings of the instance that makes me believe that it might be related to IAM role assignment, but that's not something that was changed. Not sure if that's a possibility. Instance state is "Running" to eliminate the obvious.
Any ideas for what could be causing the issue?
Thank you for your time!
- Newest
- Most votes
- Most comments
Can RDP be performed even if the instance is stopped and started?
Also, what errors do I get on the client side when I make an RDP connection?
Please check the following documents for general troubleshooting methods.
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/troubleshoot-connect-windows-instance.html#rdp-issues
This is probably just an oversight, you talk about not being able to RDP but the screenshot is of an error when you try to use Session Manager.
Assuming it's RDP that you're trying to use, be aware that each time an EC2 is stopped and then started its public IP (and public DNS) will change. Check you're using the current address when trying to connect.
Relevant content
- asked a year ago
- asked 7 months ago
AWS OFFICIALUpdated 3 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
