You must complete additional steps or you won't be able to boot the original instance after If your temporary instance is based on the same AMI that the original instance is based on, Instance that is not configured for AWS Systems Manager, use AWSSupport-ExecuteEC2Rescue, or use the following manual steps: You can useĪWSSupport-TroubleshootRDP to disable the Windows Firewall profiles using SSM Agent. We recommend that you disable Windows FirewallĪnd control access to your instance using security group rules. Verify that Windows Firewall, or other firewall software, is not blocking ForĬustom route table (Internet Gateways) in the Traffic destined outside the VPC to the internet gateway for the VPC. Verify that the route table for the subnet has a route that sends all ( Amazon EC2 User Guide for Linux Instances). Verify that the instance has passed status checks. That you missed a character or got an extra white space character when you Not work, try typing them manually when prompted. If you copied the password but get the error Your credentials did More information, see Create a security group. Verify that your security group has a rule that allows RDP access. Windows Server 2008 SP2 AMI or earlier, your instance is not automaticallyĬonfigured to recognize an IPv6 address assigned to the instance.

IPv6 address and is configured to use IPv6. To connect to your instance using an IPv6 address, check that your local computer has an If not, you canĪssociate an Elastic IP address with your instance. Verify that your instance has a public IPv4 address.

You do not see a public DNS name, you must enable DNS hostnames. (IPv4) in the details pane.) If your instance is in a VPC and

(In the Amazon EC2Ĭonsole, select the instance and check Public DNS Verify that you're using the correct public DNS hostname.

Microsoft remote desktop manager 2012