Skip to content

Installing PCoIP Management Console into AWS EC2

The PCoIP Management Console AMI is a conversion of the OVA file into the Amazon Machine Image (AMI) format with SSH enabled to permit secure administrative access.

The virtual machine is made available for users of the PCoIP Management Console that wish to move more of their deployment to the cloud—especially those deploying Amazon WorkSpaces with PCoIP Zero Clients.

Non-System Requirements

  • Amazon Web Services account with access to deploying EC2 instances

  • SSH client

Deployment Considerations

Ensure you have the Port Numbers opened and all inbound ports are restricted to your corporate network and you meet the System Configuration requirements for your PCoIP Management Console.

Important: PCoIP Management Console must not be accessible from unsecured networks

The PCoIP Management Console must only be accessible by endpoints from the open Internet as described within the PCoIP Management Console Administrators' Guide. Any other exposure to the open Internet is an unsupported use of the product and will void any warranty.

Info: Notable network behaviors

Network usage can be higher when firmware is being uploaded to endpoints. A permanent web socket connection is maintained to every online endpoint

Deployment

To deploy PCoIP Management Console AMI:

  1. Log in to AWS Console.

  2. Choose the region the AMI resides in.

  3. Navigate to EC2.

  4. Navigate to AMIs.

  5. Search Public AMIs for the AMI ID in your region. A list of AMI ID's are presented when clicking on the AMI download button seen after accepting the EULA from the Management Console download section of the support site.

  6. Select the PCoIP Management Console AMI and click Launch.

  7. Choose an Elastic Network Adapter (ENA) supported instance type (m5.xlarge recommended - see system requirements).

  8. Configure the AWS Launch steps 2-5 as appropriate for your organization.

  9. Select or create a security group in step 6 that will provide access to the required ports, with the inbound ports restricted to only your corporate network. Ensure network access is appropriate such that administrators are able to access ports 22 and 443, and that endpoints can access port 5172.

    Important: Connectivity issues

    If you are unable to get this access working, you will need to review your VPC configurations (VPCs, Subnets, Route Tables), Security configurations (Network ACLs, Security Groups), and possibly VPN Connections or Direct Connect settings.

  10. Complete the steps.

  11. When Launching, select a keypair. To ssh into the instance you will use the user admin in conjunction with the keypair you used on launch.

  12. After accessing Management Console via an SSH client such as PuTTY, follow the same migration steps Moving between IPv4 and IPv6 for switching IPv4 to IPv6 and vice versa.

  13. After the Management Console is deployed, it is important the system is appropriately secured.

Accessing Management Console Web UI

You cannot access Management Console Web UI using ports 8080 or 8443

Related Information

Securing PCoIP Management Console User Passwords

Default CentOS Configuration for PCoIP Management Console

Setting up Security

Managing Licenses Online

PCoIP Management Console Remote Endpoint Management (Enterprise)