(2025.09 and earlier) Users can manually type in instance type to launch restricted instance type

[Murielxun]

Bug description

When launching or updating VDIs, users can manually type in instance type to launch restricted instance type at software stack level.

Affected versions

2025.09 and earlier

Mitigation

1. Download patch.py, instance_type_cluster_manager.patch, and instance_type_vdc_controller.patch by replacing <output-directory> with the directory to download the patch script and patch file, <res_version> with the RES version, and <environment-name> with the name of your RES environment in the command below:
   a. The patch applies to RES 2025.09 and earlier
   b. The patch script requires AWS CLI v2, Python 3.9.16 or above, and Boto3.
   c. Configure the AWS CLI for the account / region where RES is deployed, and make sure that you have S3 permissions to write to the bucket created by RES.

OUTPUT_DIRECTORY=<output-directory>
ENVIRONMENT_NAME=<environment-name>
RES_VERSION=<res-version>
ACCOUNT_ID=<account-id>

mkdir -p ${OUTPUT_DIRECTORY}
curl https://research-engineering-studio-us-east-1.s3.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patch.py --output ${OUTPUT_DIRECTORY}/patch.py
curl https://research-engineering-studio-us-east-1.s3.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patches/instance_type_cluster_manager.patch --output ${OUTPUT_DIRECTORY}/instance_type_cluster_manager.patch
curl https://research-engineering-studio-us-east-1.s3.amazonaws.com/releases/${RES_VERSION}/patch_scripts/patches/instance_type_vdc_controller.patch --output ${OUTPUT_DIRECTORY}/instance_type_vdc_controller.patch

2. Navigate to the directory where the patch script and patch file are downloaded. Run the following patch command:

python3 ${OUTPUT_DIRECTORY}/patch.py --environment-name ${ENVIRONMENT_NAME} --res-version ${RES_VERSION} --module cluster-manager --patch ${OUTPUT_DIRECTORY}/instance_type_cluster_manager.patch

python3 ${OUTPUT_DIRECTORY}/patch.py --environment-name ${ENVIRONMENT_NAME} --res-version ${RES_VERSION} --module virtual-desktop-controller --patch ${OUTPUT_DIRECTORY}/instance_type_vdc_controller.patch

3. Restart the Cluster Manager instance for your environment. You may also terminate the instance from the Amazon EC2 Management Console.

INSTANCE_ID=$(aws ec2 describe-instances \
    --filters \
    Name=tag:Name,Values=${ENVIRONMENT_NAME}-cluster-manager \
    Name=tag:res:EnvironmentName,Values=${ENVIRONMENT_NAME}\
    --query "Reservations[0].Instances[0].InstanceId" \
    --output text)
 
aws ec2 terminate-instances --instance-ids ${INSTANCE_ID}

4. Restart the Virtual Desktop Controller instance for your environment. You may also terminate the instance from the Amazon EC2 Management Console.

INSTANCE_ID=$(aws ec2 describe-instances \
            --filters \
            Name=tag:Name,Values=${ENVIRONMENT_NAME}-vdc-controller \
            Name=tag:res:EnvironmentName,Values=${ENVIRONMENT_NAME}\
            --query "Reservations[0].Instances[0].InstanceId" \
            --output text)

aws ec2 terminate-instances --instance-ids ${INSTANCE_ID}

5. Verify the Cluster Manager instance and Virtual Desktop Controller instance status by checking the activity of the auto scaling groups starting with the name <RES-EnvironmentName>-cluster-manager-asg and <RES-EnvironmentName>-vdc-controller-asg. Wait until the new instances are launched successfully.

[Mohjeet]

Fix has been included in 2025.12 release.