Directly contact our Support Team

Recommended virtual machines sizes for GravityZone Elite deployment in Azure

This article presents the recommended virtual machines sizes for GravityZone Elite deployment in Microsoft Azure.

The size of the virtual machine you are using for deploying GravityZone Elite in Azure depends on the number of endpoints you are planning to protect, the type of deployment (all-in-one or distributed) and the type of integration.

The following table displays the Azure virtual machine sizes recommended for GravityZone deployments that include the following roles: Update Server, Web Console (Control Center), Communication Server, and Database.

Number of endpoints (up to) Azure VM size vCPU RAM (GB)
 250 Standard_F8s_v2 8 16
Standard_F8s 8 16
Standard_F16s_v2 16 32
Standard_F16s 16 32
 500 Standard_F16s_v2 16 32
Standard_F16s 16 32
 1,000 Standard_F16s_v2 16 32
Standard_F16s 16 32
 3,000 Standard_F16s_v2 16 32
Standard_F16s 16 32
 5,000 Standard_F32s_v2 32 64
 10,000 Standard_F32s_v2 32 64
 25,000 Standard_F64s_v2 64 128
 50,000 Standard_F64s_v2 64 128

 

important Important:
These VM sizes support GravityZone deployments without the Incidents Server role installed. This role requires the following resources:
  • 2 vCPU and 2 GB RAM for deployments up to 3000 endpoints
  • 4 vCPU and 2 GB RAM for deployments up to 10,000 endpoints
  • 6 vCPU and 4 GB RAM for deployments up to 50,000 endpoints
  • 30 GB of additional disk space for the Database role, regardless of deployment.

For distributed GravityZone deployments, with various configurations and integrations, refer to the Requirements > GravityZone Virtual Appliance > Hardware section in Installation Guide.

For the procedure of deploying GravityZone in Azure, refer to this KB article.

Can't find a solution for your problem? Open an email ticket and we will answer the question or concern in the shortest time possible.

Rate this article:

Submit