Prepare AWS
To assist with the smooth integration of your AWS platform with the HyWorks Controller, use the following references:
Supported Feature Matrix
| Feature | Sub Feature Category | Sub Feature | AWS |
|---|---|---|---|
| Deploy pool with existing VMs | - | - | Yes |
| Desktop VM Provisioning | Clone Type | Linked Clone | Not Applicable |
| Full Clone | Yes | ||
| Clone from Snapshot | - | No | |
| Disk persistence | Persistent VM Deployment | Yes | |
| Non-persistent VM Deployment | No | ||
| Enable DVM Reset | No | ||
| Deployment Setting | Only resource group, not Location | ||
| Customization | Both (Sysprep and Hyprep) | ||
| IP Address Filter | Yes | ||
| Shared hosted desktop provisioning and automated deployment | Yes | ||
| Automated power management and scaling | Yes | ||
| Desktop Power Operations | - | - | Yes |
| Operating Systems Support on Provider | Windows Desktops | Windows 7 | Yes |
| Windows 8.1 | Yes | ||
| Windows 10 | Yes | ||
| Windows 11 | Yes | ||
| Windows Servers | Windows Server 2008 R2 | Yes | |
| Windows Server 2012 R2 | Yes | ||
| Windows Server 2016 | Yes | ||
| Windows Server 2019 | Yes | ||
| Windows Server 2022 | Yes | ||
| Linux Desktops | CentOS 7 | Yes | |
| Ubuntu 16.04/1 | Yes | ||
| Ubuntu 18.04/1 | Yes | ||
| Ubuntu 20.04/1 | Yes | ||
| RHEL v7.9 | Yes |
Pre-requisites
-
AWS Account ID: The AWS Account ID is the unique identifier of an account created and granted as an IAM User.
-
AWS Secret Key: An AWS secret is a password known only to your IAM User. It protects your resources by granting tokens only to authorized requestors.
-
AWS Access ID: The Access Key ID is part of Access keys, which are long-term credentials for an IAM user. The AWS Secret Key and AWS Access ID together form Access keys.
-
Region: The region is a physical location worldwide where virtual Desktops will be stored.
Configure AWS IAM User
-
Log in here with your credentials: https://console.AWS.amazon.com/
-
Find the Identity and Access Management (IAM): https://console.AWS.amazon.com/iamv2/home?#/home
-
Go to Identity and Access Management (IAM)
-
Go to Users and click Add Users.
-
Add Username and Password and click Next.
-
Add User Permission:
- AmazonEC2FullAccess
- AWSConnector
- ResourceGroupsandTagsEditorFullAccess
-
Save the Credentials and download the CSV.
-
The downloaded CSV will contain the User Name (Application ID), Secret access key (Secret), and Access key ID (TenantId).
Reference: https://docs.AWS.amazon.com/IAM/latest/UserGuide/id_users_create.html
Configure Controller for Domain Account Authentication in Proxy server
Make the following configurations in the Controller when you configure the proxy server on the Controller and the AWS-based Desktop Provider is being used
-
Install the controller service using this account (not the Local System account)
- The account should be configured as "Logon as Service."
- Configuration can be done at the time of installation or later.
- The specified account will be used to authenticate through the proxy server.
- Whitelist URLs are mentioned above.
Fig: Configuration post-installation
<system.net>
<defaultProxy>
<proxy usesystemdefault="true" />
</defaultProxy>
</system.net>
- Verify the above configuration in the HyWorks controller
x:\Program Files (x86)\Accops\HyWorks\Service\EDC.Service.exe.config
Fig: Configuration file change
Note
- You need to log in again to apply the above-mentioned changes.
Desktop Operation Support
| Operation | Support | Status on AWS | Status on HyWorks |
|---|---|---|---|
| Power On | Yes | Powered On | Powered On |
| Power Off | Yes | powered Off | powered Off |
| Shutdown | Yes | powered Off | powered Off |
| Restart | Yes | Restart | Restart |
| Reset | No | - | - |
| Refresh (Desktop Information on HyWorks) | Yes | - | Update VM details, call the DVM agent |
| Re-Create (single VM from Desktop VMs page) | Yes | - | - |
Limitation with AWS Handler
-
Change the Location (the current VM will be cloned in the source VM location)
-
The Gold Master Disk should be a managed disk.
Multi-availability Zone Deployment Requirements
The customer may try to deploy HyWorks Controllers or its other components, e.g., session host servers, or personal virtual desktops, for fault tolerance.
-
HyWorks will not require any special configurations when being deployed in a distributed manner across availability zones
-
Appropriate port requirements for effective communication between HyWorks components must be maintained for deployments across different availability zones.