EC2 instance inaccessible after RDP change

My RDP port was changed in the registry of my EC2 Windows Server instance, and now the server is inaccessible after a reboot. Is there any way to recover the instance to how it was before? The securitygroup allows the new port and is assigned to the server.

Topics: Compute
Tags: Amazon EC2
Language: English

User-6791210

asked 6 years ago543 views

1 Answer

Newest
Most votes
Most comments

Are these answers helpful? Upvote the correct answer to help the community benefit from your knowledge.

Took some doing, but I spun up a new instance, mounted the dead server's disk, and changed the registry setting back. Back in business. Will be doing snapshots in the future. :)

User-6791210

answered 6 years ago

Relevant content

Change RDP port in Lightsail server and now no connection
Accepted Answer
delphiman
asked 2 years ago
Unstable network on EC2 WIndows server after scheduled reboot
Dave G
asked a year ago
Lost RDP access after EC2 instance type change
ii-Tommy
asked 3 years ago
Unable to connect to my Windows Server instance through Windows Remote Desktop
User-1567040
asked 10 months ago
How do I troubleshoot an RDP connection or instance status check failure on Windows Server after I change the EC2 instance type?
AWS OFFICIALUpdated 2 years ago
How can I restore a corrupt registry on my EC2 Windows instance?
AWS OFFICIALUpdated 4 years ago
How do I resolve the "remote session was disconnected" error that I receive when I use RDP to connect to an Amazon EC2 Windows instance?
AWS OFFICIALUpdated 6 months ago
How do I troubleshoot authentication errors that occur when I use RDP to connect to an Amazon EC2 Windows instance?
AWS OFFICIALUpdated a month ago
Change Windows EC2 instance default screen resolution
EXPERT
MikeLim
published a year ago
How do I set up Microphone and Camera access in EC2 Windows Server Instances?
EXPERT
Phanindra V
published 4 months ago

EC2 instance inaccessible after RDP change

Add your answer

Relevant content