CoPilot VM Instance Sizing

The requirements listed below are intended as a general guide only. You can use the sizing guidelines during and after CoPilot deployment.

After you have deployed CoPilot, it is important to monitor the indexing of data traffic in your specific environment and adjust configuration settings, such as index retention periods, to optimize instance sizing for your business needs.

It is also recommended to upgrade the size of virtual machines if Aviatrix platform global health alerts are triggered frequently. For information about platform global health alerts, see Global Network Health Alert.

For information about system requirements for CoPilot instances, such as inbound security rules and outbound access, see Instance (Virtual Machine) System Requirements for CoPilot.

Instance (Virtual Machine) Sizing for CoPilot

The following is information for selecting the instance (virtual machine) size for your CoPilot deployment.

You must consider how much memory and CPU you require for your CoPilot instance (virtual machine). The configuration of the virtual machine depends on the scale and the kind of networking infrastructure you have.

Work with your Aviatrix Sales representative to determine your sizing requirements. While this section provides minimum requirements and guidelines for minimum sizing based on a number of gateways, it is strongly recommended to reach out to your Aviatrix Sales representative to discuss your specific sizing needs.

Minimum Instance (VM) Size for Single CoPilot

For a simple deployment (single instance/VM), CoPilot requires a minimum of:

Minimum Instance Sizing for a Single CoPilot
Requirement Minimum Value

Memory & CPU

32 GB of RAM (or more)*

8 vCPUs (or more): for example, m5n.2xlarge

Examples:

  • Amazon EC2 instance type: m5n.2xlarge (or M5 instances if M5N is not available)

  • Google Cloud: n2-standard-8

  • Oracle Cloud Infrastructure: VM.Standard3.Flex (8core x 32G mem)

  • Microsoft Azure virtual machine: Standard_D8_v4

Data Disk

1 attached disk/volume for storage — See CoPilot Disk (Volume) Management.

Minimum Instance (VM) Size for CoPilot Based on Existing Gateways

If you are deploying CoPilot for the first time (new launch) and have existing Aviatrix gateways, below are the general guidelines for a minimum VM size based on the number of existing gateways in an infrastructure.

The information below is intended as a general guide only. After you deploy CoPilot, you will be able to monitor the indexing of data for traffic in your specific environment and tune configuration settings, such as index retention periods, that will help determine the best instance sizing for your business needs.
Instance Sizing Guideline for CoPilot Based on Existing Gateways
Number of Existing Aviatrix Gateways Single Instance Requirements

Less than 500

  • 32 GB of RAM or more

  • 8 vCPUs or more

  • Example Instances:

    • AWS: m5n.2xlarge or M5

    • GCP: n2-standard-8

    • OCI: VM.Standard3.Flex (8 core, 32 GB mem)

    • Azure: Standard_D8_v4

500 and more

  • 64 GB of RAM or more

  • 16 vCPUs or more

  • Example Instances:

    • AWS: m5n.4xlarge or M5

Instance (VM) Considerations for CoPilot

Note the following points about CoPilot VM requirements:

  • (AWS) For CoPilot ARM-based images, Amazon EC2 A1 instances are currently not supported.

  • (AWS) For CoPilot ARM-based images, Private Mode is currently not supported.

  • (Azure) When provisioning CoPilot with Azure, ‘burstable’ (B series) or ‘slow disk’ instances are not recommended.

  • For a simple deployment, the single instance (VM) must meet the minimum requirements.