Skip to main content

Virtual MachinesAmazon Web Services Setup Guide

Table of Contents

Request AMIs to Deploy in AWS

Exabeam has created Amazon Machine Images (AMIs) to deploy your solution. To request access to the AWS image files, visit the Virtual Images section in the Exabeam Community. You will need to provide the following information:

  • Customer email address

  • AWS customer account number

  • AWS region of deployment

  • Exabeam product to be deployed

Note

Please review all specifications for your deployment and ensure you have sufficient resources (CPU, memory, and storage across all the instances that will be deployed in your account) to deploy the Exabeam AMIs. Additionally, please ensure you have valid Exabeam licenses for the product(s) you will implement.

Exabeam Platform Specification Table for Virtual Platforms

These are the minimum operating specifications needed to run your Exabeam product. We do not support hybrid deployments (cross environment deployments). All nodes must be in the same subnet.

Be aware that vCPU is not the same as the number of CPUs or Cores for the processor. A vCPU is typically equal to the number of threads in the processor. Also, a hard drive GiB unit (used in AWS) is fractionally larger than a standard GB (1 GiB ~ 1.074 GB).

The tables below details the CPU and memory allocation required for Exabeam products to operate optimally, with the following provisioned:

  • The host is not shared with any other product or resource.

  • All virtual appliances must be approved by Exabeam prior to deployment.

  • Storage requirements:

    • Use local drives or an NAS or SAN with a 10Gbit/s link (iSCSI or Fibre Channel) and block storage access; the underlying drives must also meet the SSD/HDD IO performance requirements.

      Important

      Configuration and maintenance of NAS/SAN is the responsibility of the customer. Exabeam cannot debug issues related to misconfiguration or performance with NAS/SAN.

      Important

      NFS is not supported.

    • Do not use VMFS with extents spread across multiple drives and managed by ESX.

    • To avoid performance issues, SSD drive files MUST be put on an SSD backed data store.

      Note

      To ensure adequate virtual drive capacity, a 10% additional storage buffer is required on the physical drives. For example, when an OVA requires 215 GB of virtual space, the appliance requires a physical drive with 236.5 GB of space.

    • Disk storage must be configured with thick provisioning (eager zeroed recommended). Snapshots are not supported because they switch the environment from thick to thin provisioning.

  • Network requirements:

    • Network card must support paravirtualization (VMXNet v.3 adapters).

Advanced Analytics Node Type

AWS

Physical Master Node including Hypervisor

Virtual Hypervisor

4 vCPU

Memory: 10 GB

1 x 32 GB (SSD)

OVA Virtual Master Node

Instance type: r4.16xlarge

Core: 64 vCPU

Memory: 488 GiB (~ 523 GB)

Storage: Our AMI allocates the following hard-drives:

  • 1 x 120 GiB GP2 (SSD)

  • 3 x 894 GiB GP2 (SSD)

  • 6 x 1860 GiB GP2 (SSD)

Virtual Hypervisor

4 vCPU

Memory: 10 GB

1 x 32 GB (SSD)

OVA Virtual Worker Node

Instance Type: r4.4xlarge

Core: 16 vCPU

Memory: 122 GiB (~ 130 GB)

Storage: Our AMI allocates the following hard drives:

  • 1 x 120 GiB GP2 (SSD)

  • 3 x 894 GiB GP2 (SSD)

  • 6 x 1860 GiB GP2 (SSD)

Table 1. Advanced Analytics Node Specifications


Node Type in Exabeam Cluster

AWS

Virtual Hypervisor

OVA Virtual Master or

Worker Node

Instance type: r4.8xlarge

Core: 32 vCPU Memory: 244 GiB

Storage: Please ensure you follow the ordering of storage disks as listed below. Our AMI allocates the following hard-drives:

  • 1 x 150 GiB GP2 (SSD)

  • 2 x 2000 GiB GP2 (SSD)

  • 9 X 4 000 GiB ST1 (HDD)

Table 2. Data Lake Node Specifications


For clusters with 21 nodes or more, an additional three management nodes are required for cluster management operations, health monitoring and other critical functions.