search

aws-quickstart / quickstart-microsoft-rdgateway

AWS Quick Start Team
Apache License 2.0
48 stars 87 forks source link

changing RDGW instance type to t3a.small causes termination #24

Open rosenbluh opened 4 years ago

rosenbluh commented 4 years ago

I attempted to rightsize the RDGW from 8GB since it was using very little RAM. I changed it to a t3a.small and tried to start it. I received a message that the instance type was incompatible, I refreshed and saw that the instance was terminated. The public IP address showed as unassociated.

Is there anything that can be done to address this from the QuickStart? I don't know why this happened, but I think it has happened to me before.

A few ideas in case there is no technical solution or the problem lies with AWS design:

  1. Offer .medium instances and make this the default for RDGWs
  2. Make a note in the documentation, perhaps with a list of other precautions when deploying this quickstart (I am making a list)
  3. Document this in tags noting the compatibility

This is the system log showing only the initial start.

2019/11/07 16:23:32Z: Windows sysprep configuration complete.
2019/11/07 16:23:35Z: Message: Waiting for meta-data accessibility...
2019/11/07 16:23:35Z: Message: Meta-data is now available.
2019/11/07 16:23:37Z: AMI Origin Version: 2019.10.09
2019/11/07 16:23:37Z: AMI Origin Name: Windows_Server-2016-English-Full-Base
2019/11/07 16:23:38Z: OS: Microsoft Windows NT 10.0
2019/11/07 16:23:38Z: OsProductName: Windows Server 2016 Datacenter
2019/11/07 16:23:38Z: OsInstallOption: Full
2019/11/07 16:23:38Z: OsVersion: 10.0
2019/11/07 16:23:38Z: OsBuildLabEx: 14393.3269.amd64fre.rs1_release.190929-1234
2019/11/07 16:23:38Z: Language: en-US
2019/11/07 16:23:38Z: TimeZone: Coordinated Universal Time
2019/11/07 16:23:38Z: Offset: UTC 00:00:00
2019/11/07 16:23:38Z: AMI-ID: ami-0df99cdd65bce4245
2019/11/07 16:23:38Z: Instance-ID: i-0c9e2e96005d7dcc9
2019/11/07 16:23:38Z: Instance Type: m4.large
2019/11/07 16:23:42Z: Driver: AWS PV Driver Package v8.3.2 
2019/11/07 16:23:42Z: Driver: Intel(R) 82599 Virtual Function v2.0.210.0 
2019/11/07 16:23:42Z: Launch: EC2 Launch v1.3.2001360
2019/11/07 16:23:42Z: SSM: Amazon SSM Agent v2.3.634.0
2019/11/07 16:23:43Z: RDPCERTIFICATE-SUBJECTNAME: EC2AMAZ-OA3DQG4
2019/11/07 16:23:43Z: RDPCERTIFICATE-THUMBPRINT: 6C554062536E7DAA97151D01E5EDA6396F72A58D
2019/11/07 16:23:56Z: HibernationEnabled: false
2019/11/07 16:23:56Z: Username: Administrator
2019/11/07 16:23:56Z: Password: <Password>
NlfobVz3SFbxDfEZqgOmsATgskaDUdyvNx3FEcQL/sRNYprTZuk/fDNvmdG/UQnr4hI5zQo2ZKDKihDMihLumHFgyL7yCZ4Ao9tVzrcnkkmbcCRP2t+BdF1FK6ZNYYKeKO2YdUBN+0es1sd+XIM5+nE6qF4sqGOtEkmRwG3LXhyFzPjqbnGJHa5Pf1Zf2mYEQTIUsKhf++EOGKq3o5cPBoXbR6EYSy2Ulr9p6nZMT+zxK0z/DEgejj/HZVqi7j8laSn8/0/Edl7FiH5AYAz2ewfAf6z1sWNW2CxaFVvqR3UYQr8D4iw47byQzgRcYs7JOjiaAd+V3JoO1AkOlcQbDQ==
</Password>
2019/11/07 16:23:58Z: Message: Windows is Ready to use
rosenbluh commented 4 years ago

It turns out that a new instance started and got joined to the domain as a new IP and host name. This provided an opportunity to replicate this behavior.

Instance ID i-07fc32b33ff549b76
Instance Type   
 EBS-optimized
An error occurred while trying to change the ebs optimized support of this instance
The instance 'i-07fc32b33ff549b76' is not in the 'stopped' state.

Then I tried changing it to t3a.medium

Instance ID i-07fc32b33ff549b76
Instance Type   
 EBS-optimized
An error occurred while trying to change the ebs optimized support of this instance
The instance 'i-07fc32b33ff549b76' is not in the 'stopped' state.

I found this AWS forum post that was not answered.

I refreshed again and found this instance terminated and another one spun up now on another RDGW spun up but this time on a new public IP address. I guess it picks a public IP address at random rather than trying to use the former IP address attached to the VM.

I would like to know how to rightsize the RDGWs.