Deploying vis|ability in the Cloud
Overview
vis|ability can be deployed using cloud-hosted infrastructure, providing an alternative to hosting the core System Manager on a physical server at the customer location.
In a typical cloud deployment, the vis|ability System Manager is hosted within a cloud-based virtual machine, while Display Nodes, user workstations, Capture Clients, and other endpoints remain wherever they are operationally required.
This architecture can reduce the need for dedicated server hardware at individual locations while allowing multiple sites and users to connect to a centralized vis|ability environment.
The current System Manager architecture supports physical server, virtual machine, and cloud deployment models.
What Runs in the Cloud?
The primary component hosted in the cloud is the vis|ability System Manager and its supporting services.
System Manager provides the centralized services required by the vis|ability environment. End-user components connect back to the System Manager using the configured System Address. For a cloud-hosted deployment, this becomes the Cloud System Address used by endpoints when they are installed and registered. vis-ability Installation and Co…
The rest of the vis|ability system does not necessarily need to reside in the cloud.
For example, Display Nodes remain associated with the displays they drive, while Desktop Client, Capture Client, Administration Client, and Base Client are installed on the workstations where those capabilities are required.
This creates a distributed architecture with a centralized cloud-hosted System Manager.
Cloud System Manager Requirements
A cloud-hosted System Manager should meet the following baseline requirements:
| Resource | System Manager Requirement |
|---|---|
| CPU | 12 cores |
| Memory | 32 GB RAM |
| Storage | 512 GB high-speed storage |
| Networking | Virtual networking equivalent to 1 Gbps |
| Additional Networking | Multiple virtual networks/interfaces where required |
These specifications provide a starting point. Final sizing may vary based on the size and design of your vis|ability environment.
Cloud Provider - AWS
AWS has historically been used as a hosting environment for vis|ability Cloud.
The previous vis|ability cloud guidance identified an AWS EC2 t3.xlarge instance for System Manager. However, the current System Manager datasheet defines cloud requirements in terms of required compute resources rather than a specific AWS instance type.
For current deployments, the cloud instance should therefore be selected based on the current System Manager requirements and the intended system workload, rather than relying solely on the older t3.xlarge designation.
Note: Cloud instance families and configurations change over time. The selected instance should be validated against the current vis|ability System Manager requirements during system design.