Prerequisites
Before enabling and using Thinfinity® Cloud Manager, ensure your environment meets the infrastructure, licensing, and permission requirements described in this article.
Completing these prerequisites reduces setup friction and avoids common activation errors. If you are deploying Cloud Manager in a production environment, review each section carefully before proceeding.
Thinfinity Workspace Requirements
Cloud Manager is an integrated module of Thinfinity® Workspace. A fully operational Workspace deployment is required before Cloud Manager can be activated.
| Requirement | Details |
|---|---|
| Workspace version | v8.0 or later |
| Primary Broker | Installed, configured, and reachable. |
| Web Manager | Accessible via browser. |
| Secondary Broker | Required for VDI/DaaS model deployments and direct VM connections. At least one Secondary Broker must be registered and online. |
| Virtualization Agent | Required on each VM intended for the Agent ID connection mode. The agent runs inside the VM and registers with the Secondary Broker; without it, only Public IP and Private IP connection modes are available. |
For a full description of Thinfinity Workspace components and their roles, see the Thinfinity Workspace product manual.
Multi-Broker and HA Deployments
If your Thinfinity® Workspace deployment uses multiple brokers — for high availability behind a load balancer, or to serve resources across regions, organizational units, or cloud accounts — the deployment-level architecture decisions are documented in the Thinfinity Workspace Best Practices for Production Environments section of the Workspace manual. Cloud Manager runs on top of that architecture; this manual covers Cloud Manager-specific configuration only.
The remaining prerequisites in this article apply to all deployments, single-broker or multi-broker.
Licensing
Cloud Manager requires an active license that includes the Cloud Manager module. Verify your license status before attempting activation.
To check your license:
- Open Configuration Manager.
- Navigate to License.
- Confirm that Cloud Manager appears as an active module.
If Cloud Manager does not appear in your license, contact your Cybele Software reseller or support team to obtain an updated license file.
Administrative Access
The administrator performing the setup must have the following access:
| Access | Requirement |
|---|---|
| Thinfinity Workspace admin account | Full administrative access to Configuration Manager and Web Manager |
| Cloud Manager permissions | Full administrative permissions on all Cloud Manager entities, namely: View / Create / Edit / Delete on Models, Credentials, and Deployments, plus View / Manage on Instances. See Cloud Manager Permissions for the per-entity flag set and the Full Administrator profile. |
| Cloud provider credentials | IAM credentials, service account keys, or API tokens corresponding to each cloud provider or hypervisor intended for connection |
uses a dedicated permission layer on top of the standard Thinfinity Workspace RBAC system. For details on how to configure administrative access to Cloud Manager, see Cloud Manager Permissions.
Cloud Provider and Hypervisor Requirements
Each provider or hypervisor you intend to connect has its own credentials and network configuration. The table below summarizes the minimum requirements.
| Provider / Hypervisor | Credential Type | Network Requirement |
|---|---|---|
| AWS (EC2) | IAM user with programmatic access (Access Key ID + Secret) | Outbound HTTPS to AWS APIs |
| Microsoft Azure | Service Principal (App Registration) with Contributor role | Outbound HTTPS to Azure Resource Manager |
| Google Cloud Platform | Service Account JSON key with Compute Engine permissions | Outbound HTTPS to GCP APIs |
| IONOS Cloud | Username/password or API token | Outbound HTTPS to IONOS Cloud API |
| Oracle Cloud | API Key + tenancy/user OCIDs + fingerprint, or Instance Principal | Outbound HTTPS to Oracle Cloud APIs |
| Oracle KVM (oVirt / OLVM) | oVirt user account in username@domain format |
Network access from the Thinfinity Workspace server to the oVirt/OLVM engine on TCP 443 |
| VMware (ESXi / Horizon) | vCenter Server admin credentials | Network access from the Thinfinity Workspace server to vCenter on TCP 443 |
| Microsoft Hyper-V | Windows admin credentials with Hyper-V Manager access | Network access from the Thinfinity Workspace server to the Hyper-V host on WinRM (TCP 5985 or 5986) |
| Proxmox VE | Proxmox user account or API token | Network access from the Thinfinity Workspace server to the Proxmox host on TCP 8006 |
| Verge.IO | Username/password or OIDC | Network access from the Thinfinity Workspace server to the Verge.IO host on TCP 443 |
Detailed credential fields and configuration steps for each provider are documented in the Credentials section.
Network and Firewall Requirements
Ensure the following network paths are open before configuring credentials or deploying VMs:
| Traffic | Source | Destination | Port / Protocol |
|---|---|---|---|
| Cloud provider API calls | Thinfinity Workspace server | Cloud provider API endpoints | TCP 443 (HTTPS) |
| VM connection (Public IP mode) | Gateway | VM public IP | TCP 443 or RDP/RFB port |
| VM connection (Private IP mode) | Secondary Broker | VM private IP | TCP 443 or RDP/RFB port |
| VM connection (Agent ID mode) | Secondary Broker | Virtualization Agent on VM host | TCP 443 (HTTPS) |
| Hypervisor management (on-prem) | Thinfinity Workspace server | ESXi / Hyper-V / Proxmox / oVirt / Verge.IO host | Provider-specific management port |
If your Thinfinity Workspace deployment uses multiple Secondary Brokers, verify that each broker that will manage cloud workloads has the required network paths open.
Browser Requirements (Web Manager)
Cloud Manager is accessed through Web Manager. No additional browser plugins are required. The following browsers are supported:
- Google Chrome (latest)
- Microsoft Edge (Chromium, latest)
- Mozilla Firefox (latest)
What’s Next
Once all prerequisites are met, proceed to activate the module: