AWS Cloud Deployment Specifications
Overview
This document lists the hardware specifications for deployment of version 3.5.4 of the MLOps Platform ("the platform") on the Amazon Web Services (AWS) cloud; for details, refer to the AWS documentation.
- All references to AWS cloud apply also to AWS Outposts, except where otherwise specified.
- AWS platform deployments also require an Elastic IP address. For more information, see the AWS documentation.
- All capacity calculations in the hardware specifications are performed using the base-10 (decimal) number system. For example, 1 TB = 1,000,000,000,000 bytes.
-
Provisioning of the servers is handled automatically by the platform installer (Provazio).
Don't attempt to provision the servers manually prior to the deployment. -
The data-node instances include Non-Volatile Memory Express (NVMe) SSD-based instance storage, which is optimized for low latency, very high random I/O performance, and high sequential read throughput. The data doesn't persist on the NVMe if the instance is stopped.
Don't attempt to shut down any of the data nodes, as it will erase the data.
Hardware Configurations
The platform is available in two configurations, which differ in a variety of aspects, including the performance capacity, footprint, storage size, and scale capabilities:
- Iguazio Playground
A single data-node and single application-node cluster implementation. This configuration is designed mainly for evaluation trials and doesn't include high availability (HA) or performance testing.
NoteYou can deploy a Proof of Concept (POC) in the Iguazio playground configuration. Be aware that the POC cannot be used as development environment or for a production environment.
- Operational Cluster
- A scalable cluster implementation that is composed of multiple data and application nodes. This configuration was designed to achieve superior performance that enables real-time execution of analytics, machine-learning (ML), and artificial-intelligence (AI) applications in a production pipeline. The minimum requirement for HA support is three data nodes and three application nodes.
AWS Data-Node Specifications
Data nodes in platform AWS cloud deployments must use one of the following EC2 instance types and fulfill the related specifications; choose the type that best fits your requirements.
-
Component Specification vCPUs 8 Memory 61 GiB Data disks (local storage) 1 x 1.9 TB NVMe SSD OS boot disk (EBS volume) General Purpose SSD (gp2); 400 GB (minimum) Usable storage capacity Single data node (Playground) — 1 TB
3 nodes (Operational Cluster) — 2 TB -
Component Specification vCPUs 16 Memory 122 GiB Data disks (local storage) 2 x 1.9 TB NVMe SSD OS boot disk (EBS volume) General Purpose SSD (gp2); 400 GB (minimum) Usable storage capacity Single node (Playground) — 2.5 TB;
3 nodes (Operational Cluster) — 4 TB -
Component Specification vCPUs 32 Memory 244 GiB Data disks (local storage) 4 x 1.9 TB NVMe SSD OS boot disk (EBS) General Purpose SSD (gp2); 400 GB (minimum) Usable storage capacity 3 nodes (Operational Cluster) — 9 TB
AWS Application-Node Specifications
Application nodes in platform AWS cloud deployments are supported on Elastic Kubernetes Service (EKS) and must use one of the following instance types. Choose the type that best fits your requirements. For specification details for each type, refer to the AWS documentation.
- m5 instance family (from 4xlarge and higher)
- r5 instance family (from 4xlarge and higher)
- p3.2xlarge (trial only)
- p3.8xlarge
- p3.16xlarge
- g4dn.12xlarge
- g4dn.16xlarge
Backing up the Platform
Allocate one EFS storage drive in your EKS for backing up your platform. See full details in Backing Up the Platform.