<blockquote>
  <p>Yes, You can able to re-enable RDP using run the AWSSupport-ExecuteEC2Rescue Automation (AWS Systems Manager)</p>
</blockquote>

<p><strong>Please follow below steps carefully:</strong></p>

<ol>
<li><p>Open the AWS Systems Manager console at <a href="https://console.aws.amazon.com/systems-manager/" rel="nofollow noreferrer">https://console.aws.amazon.com/systems-manager/</a>.</p></li>
<li><p>In the navigation pane, choose <strong>Automation</strong>.</p></li>
<li><p>Choose <strong>Execute automation</strong>.</p></li>
<li><p>In the documents list, choose <strong>AWSSupport-ExecuteEC2Rescue</strong>. The document owner is Amazon.</p></li>
<li><p>In the Document details section verify that Document version is set to the highest default version. For example, 13 (default).</p></li>
<li><p>In the Execution mode section, choose <strong>Simple execution</strong>. Leave the Targets and Rate Control option disabled.</p></li>
<li><p>In the Input parameters section, specify the following parameters:</p>

<p>For UnreachableInstanceId, specify the <strong>ID of the unreachable instance</strong>.</p>

<p>For LogDestination, specify an Amazon S3 bucket if you want to collect operating 
system-level logs while troubleshooting your instance. Logs are automatically uploaded 
to the specified bucket.</p>

<p>For EC2RescueInstanceType, specify an instance type for the EC2Rescue instance. The 
default instance type is t2.small.(Please leave as it is if you are confused and go 
ahead)</p>

<p>For SubnetId, specify a subnet in an existing VPC in the same availability zone as the 
unreachable instance. By default, Systems Manager creates a new VPC, but you can 
specify a subnet in an existing VPC if you want. (Please leave as it is if you are 
confused and go ahead)</p></li>
</ol>

<p><strong>Note</strong></p>

<p>If you don't see the option to specify a bucket or a subnet ID, verify that you are using the latest Default version of the document.</p>

<p>For AssumeRole, if you created roles for this Automation by using the CloudFormation procedure described earlier in this topic, then specify the AssumeRole ARN that you copied from the CloudFormation console.</p>

<ol start="8">
<li>Choose Execute automation.</li>
</ol>

<p>It takes sometimes (5-10 minutes) and you are able to access your old instance with new IP.  </p>

<p>Here is the AWS documentation for this issue:
<a href="https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-remote-desktop-connection-ec2-windows/" rel="nofollow noreferrer">https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-remote-desktop-connection-ec2-windows/</a></p>

CC BY-SA 4.0
2019-02-07T06:58:52.573Z
2019-02-07T07:40:40.733Z
2019-02-07T07:40:40.733Z
Subhash
<p>Accidentally i disabled RDP on EC2 windows machine and now I am not able to access it via RDP, Is there any way to re-enable RDP service on EC2 instance?</p>

CC BY-SA 4.0
2019-02-07T06:49:51.150Z
how did you disable RDP? using which way? from windows setting ?
Harsh Manvar
CC BY-SA 4.0
2019-02-07T06:56:03.777Z
It might help you [troubleshoot-remote-desktop-connection-ec2-windows](https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-remote-desktop-connection-ec2-windows/)
Jenish Patel
CC BY-SA 4.0
2019-02-07T07:05:59.897Z
I was trying to run powershell script, Accidentally script did that.
Jay
CC BY-SA 4.0
2019-02-07T12:17:55.390Z
A link by itself is not an answer. Links can rot. Please, at least summarise what's behind the link for your answer to have lasting value to this site.
Mast
<amazon-web-services><amazon-ec2>
How to re-enable RDP on AWS-EC2 instance
Jay
# How to re-enable RDP on AWS-EC2 instance

(Asked by: username_0 on 2019-02-07)

Accidentally i disabled RDP on EC2 windows machine and now I am not able to access it via RDP, Is there any way to re-enable RDP service on EC2 instance?

**Tags:** amazon-web-services, amazon-ec2

> **Comments:**
> **username_1**: how did you disable RDP? using which way? from windows setting ?  
> **username_2**: It might help you [troubleshoot-remote-desktop-connection-ec2-windows](https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-remote-desktop-connection-ec2-windows/)  
> **username_0**: I was trying to run powershell script, Accidentally script did that.  
> **username_3**: A link by itself is not an answer. Links can rot. Please, at least summarise what's behind the link for your answer to have lasting value to this site.  

---

## 1 answers

### Answer by username_4 on 2019-02-07. Score: 3 | Accepted answer

> Yes, You can able to re-enable RDP using run the AWSSupport-ExecuteEC2Rescue Automation (AWS Systems Manager)

**Please follow below steps carefully:**

1. Open the AWS Systems Manager console at <https://console.aws.amazon.com/systems-manager/>.
2. In the navigation pane, choose **Automation**.
3. Choose **Execute automation**.
4. In the documents list, choose **AWSSupport-ExecuteEC2Rescue**. The document owner is Amazon.
5. In the Document details section verify that Document version is set to the highest default version. For example, 13 (default).
6. In the Execution mode section, choose **Simple execution**. Leave the Targets and Rate Control option disabled.
7. In the Input parameters section, specify the following parameters:

   For UnreachableInstanceId, specify the **ID of the unreachable instance**.

   For LogDestination, specify an Amazon S3 bucket if you want to collect operating
   system-level logs while troubleshooting your instance. Logs are automatically uploaded
   to the specified bucket.

   For EC2RescueInstanceType, specify an instance type for the EC2Rescue instance. The
   default instance type is t2.small.(Please leave as it is if you are confused and go
   ahead)

   For SubnetId, specify a subnet in an existing VPC in the same availability zone as the
   unreachable instance. By default, Systems Manager creates a new VPC, but you can
   specify a subnet in an existing VPC if you want. (Please leave as it is if you are
   confused and go ahead)

**Note**

If you don't see the option to specify a bucket or a subnet ID, verify that you are using the latest Default version of the document.

For AssumeRole, if you created roles for this Automation by using the CloudFormation procedure described earlier in this topic, then specify the AssumeRole ARN that you copied from the CloudFormation console.

8. Choose Execute automation.

It takes sometimes (5-10 minutes) and you are able to access your old instance with new IP.

Here is the AWS documentation for this issue:
<https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-remote-desktop-connection-ec2-windows/>


---

