Zoom Node Infrastructure Prerequisites

Refer to these prerequisites to prepare your organization for a Zoom Node deployment.

This section details hardware and software prerequisites for Zoom Node deployments, including module installation.

Building your hybrid communication foundation

Hardware and software references for each deployment scenario are provided below.

Supported Hypervisors

Understanding hypervisor compatibility allows your organization to leverage existing virtualization investments while maintaining full Zoom Node feature support.

Hypervisor Platform	Minimum Version Requirement	Strategic Implementation Considerations
VMware vSphere/ESXi	6.7 or greater	Industry-standard choice offering broadest compatibility, ideal for enterprises with existing VMware infrastructure
Proxmox VE	Proxmox 8.x or 9.0.x (VM Only/No LXC support)	Cost-effective open-source option supporting both Proxmox VE and virt-manager implementations
Nutanix AHV	AOS 6.10.x or 7.x (VM Only/No LXC support)	Optimal for organizations leveraging hyper-converged infrastructure strategies
Microsoft Hyper-V Server	Hyper-V Server 2019 or greater	Seamless integration for Windows-centric environments
AWS EC2	Current version	Seamless integration for Windows-centric environments

Contact Zoom support for specific Hyper-V version validation.

Virtual Machine Hardware Specifications

The following specifications cover standard and minimum hardware requirements.

Standard Production Configuration

This configuration enables Enterprise-level organizations to maximize Zoom Node capabilities by supporting up to four (4) concurrent Service Modules per Node.

Infrastructure Component	Technical Specification	Business Impact and Implementation Rationale
CPU Architecture	64-bit Intel E5-2650v4 or newer @ 2.0GHz+ AMD 64-bit @ 2.0GHz+	Supports real-time media processing capabilities essential for quality user experiences
Virtual CPU Allocation	8 vCPUs	Enables concurrent operation of multiple hybrid services without performance degradation
Memory Allocation	16 GB RAM	Supports memory-intensive operations including transcoding and media routing
Storage Provisioning	200 GB HDD	Accommodates OS, Service Modules, logs, and temporary media storage
Network Interface	10 GB virtual NIC	Prevents network bottlenecks during high-volume media processing scenarios

Minimum Viable Configuration

This configuration is suitable for initial testing, proof of concept, lab environments, or single-service deployments with limited concurrent usage.

Infrastructure Component	Minimum Specification	Appropriate Use Cases and Limitations
Virtual CPU Allocation	3 vCPUs	Testing environments, single-service deployments
Memory Allocation	6-8 GB RAM	Limited concurrent user support, may require scaling
Storage Provisioning	200 GB HDD	Basic storage for essential operations only
Network Interface	1 GB/s virtual NIC	Adequate for low-volume implementations

Critical Performance Consideration: Organizations must plan to scale from minimum-to-production standard specifications as usage patterns grow. Running a production system on Minimum specs is not supported and will likely cause performance or installation issues.

Network architecture and connectivity prerequisites: Ensuring reliable hybrid communications

This section outlines the mandatory network, IP addressing, and DNS requirements needed for seamless service integration and reliable communication with Zoom’s cloud infrastructure.

Fundamental Network Requirements

These non-negotiable network configurations form the foundation of successful Zoom Node implementations.

Network Requirement	Technical Specification	Critical Implementation Impact
VM Network Type	Bridged/direct VM networking mandatory	Enables direct client-to-Node communication essential for hybrid services
NAT Configuration	NOT supported - VM cannot reside behind hypervisor NAT	Prevents communication failures between clients and Zoom Node services
Internet Connectivity	Required for cloud service integration	Enables hybrid service functionality and management plane communication
Proxy Server Support	Supported for Zoom Node OS communications. Proxy support varies by Service Module family; check module documentation.	Enables reliable cloud service connectivity without intermediary complications
Internal Addressing	RFC 1918 addressing fully supported	Allows seamless integration with existing enterprise network schemes

IP Address Planning Matrix

Strategic IP address allocation enables flexible service deployment and future expansion.

Deployment Architecture	IP Address Requirements	Implementation Flexibility and Growth Path
Standard Multi-Service Node	1 unique IP per service (up to 4 total)	Maximum deployment flexibility, supports phased service rollout
Hybrid WAG Implementation	2 dedicated IP addresses required	Enables redundant Web Application Gateway services
Consolidated Deployment	1 shared IP for Node + primary module	Limited to specific low-complexity scenarios
High Availability Architecture	Multiple IPs across distributed components	Supports enterprise survivability requirements

DNS Architecture Requirements

Proper DNS configuration ensures reliable service discovery and certificate validation.

Critical DNS Implementation Requirements

• Public DNS Resolution Mandate: All Zoom Node hostnames must resolve via public DNS infrastructure

• Split-Horizon DNS Support: External DNS zones must resolve Node hostnames for Zoom cloud IP ranges

• Survivability DNS Architecture: Local DNS servers must remain available during internet outages

• Naming Consistency Requirement: Internal users and Zoom cloud infrastructure must reference identical hostnames

Implementation Best Practice: Document and validate all DNS entries before deployment to prevent certificate and connectivity issues.

Certificate management strategy: Securing your hybrid communications

This section outlines available certificate options—automated or BYOC—and provides planning guidance to align with your organization’s security policies and deployment architecture.

Strategic Certificate Management Options

Management Method	Operational Model	Optimal Use Case and Business Benefits
Auto PKI (Recommended)	Automated enrollment and renewal with Zoom-managed costs	Reduces operational overhead, eliminates certificate expiration risks, ideal for most deployments
Bring Your Own Certificate (BYOC)	Organization-managed certificates from public CAs	Enables compliance with existing PKI policies, suitable for enterprises with mature certificate management

BYOC Implementation Requirements

This section details supported certificate models and provides a planning template to ensure secure, scalable deployments across services.

Certificate Type Selection Guide

Certificate Type	Technical Capability	Implementation Example	Deployment Complexity
Wildcard Certificate	Encrypts all subdomain traffic	*.company.com covers all services	Simplified management, recommended approach
Multi-SAN Certificate	Supports up to 5 specific hostnames	Individual FQDN per service	Requires comprehensive pre-planning

Multi-Service Certificate Planning Template

Use this template to plan your certificate requirements before deployment:

Service Role	Hostname (SAN Entry)	Assigned IP Address	Certificate Coverage Notes
Zoom Node Platform	zoom-node01.company.com	10.1.50.100	Base platform requiring certificate coverage
ZPLS Service	zpls.company.com	10.1.50.100	Can share IP with Node platform
Recording Service	zoom-recording.company.com	10.1.50.101	Requires dedicated IP address
Webinar Service	zoom-webinar.company.com	10.1.50.102	Requires dedicated IP address
Future Service Slot	(Reserved for expansion)	N/A	Maintains deployment flexibility

Critical Deployment Warning: Standard single-host certificates are incompatible with Zoom Node except in the specific scenario of one shared IP/hostname between Node and a single module.

Service-specific prerequisites: Enabling advanced hybrid capabilities

This section outlines key prerequisites for deploying Zoom Node in an AWS context.

AWS Cloud Deployment Prerequisites

AWS Requirement	Technical Specification	Implementation Purpose
Workstation Capacity	Minimum 20 GB storage	Supports tool installation and image conversion
AWS CLI Tools	Latest version required	Enables automated deployment workflows
QEMU Image Tools	qemu-img utility	Facilitates VMDK to AMI conversion
IAM Configuration	vmimport role with appropriate policies	Enables secure VM import operations
S3 Infrastructure	Bucket with vmimport permissions	Provides staging for VM images

Strategic implementation planning framework

This section provides deployment profiles and scaling strategies to help you plan for performance, reliability, and long-term growth across hybrid environments.

Deployment Sizing and Capacity Planning Matrix

Select your deployment profile based on organizational size and service requirements:

Deployment Profile	Infrastructure Scale	Module Distribution Strategy	Target Use Case
Pilot/Small Office	1-2 Nodes	1-2 modules per Node	Proof of concept, under 500 users
Standard Enterprise	3-5 Nodes	2-3 modules per Node	500-5,000 users, multi-site
Large Enterprise/HA	6+ Nodes	Distributed modules, geographic redundancy	5,000+ users, mission-critical

Resource Optimization and Scaling Strategies

Maximize infrastructure investment through:

• Strategic Module Consolidation: Deploy up to 4 modules per Node with standard specifications

• Phased Scaling Approach: Begin with minimum specifications for testing, scale to production standards

• Service Criticality Assessment: Isolate mission-critical services on dedicated Nodes

• Geographic Distribution Planning: Deploy Nodes across locations for survivability and performance