Cloud-Ready

Kinetica is able to be easily deployed and scaled in a cloud environment making it cloud-ready. KAgent can be used to automatically provision as many instances as desired, install Kinetica, and link several clusters of instances together for high availability (if necessary). KAgent currently supports provisioning to the three major cloud infrastructure vendors:

By default, KAgent will provision new VMs into your public cloud account before installing Kinetica. If you already have VMs provisioned in an AWS, GCP, or Azure environment, you can use KAgent to install Kinetica on these machines as if they were on premise. However, note that these VMs should meet Kinetica's system requirements.

Supported Regions and Instances

If VMs are already provisioned within your preferred cloud vendor environment or you'd rather KAgent install to VMs you have manually provisioned (e.g., using the on premise installation path), Kinetica recommends the following instances and setup per vendor:

Important

If provisioning and installing via KAgent, the optimal storage for the Persist Tier will be automatically attached to the provisioned instances

Vendor Recommended Regions Instance Types Storage Types
AWS
  • US East 1
  • US East 2
  • US West 1
  • US West 2

The KAgent installer contains the rest of the currently supported set of regions.
  • p2.xlarge, p2.8xlarge
  • p3.8xlarge

The KAgent installer contains the rest of the currently supported set of instance types.
Azure
  • Australia East
  • Canada Central
  • Central India
  • East US
  • East US 2
  • Japan East
  • Korea Central
  • North Central US
  • North Europe
  • South Central US
  • Southeast Asia
  • UK South
  • West Europe
  • West US 2

The KAgent installer contains the rest of the currently supported set of regions.
  • Standard_NC6s_v2, Standard_NC12s_v2, Standard_NC24s_v2
  • Standard_NC6s_v3, Standard_NC12s_v3, Standard_NC24s_v3
  • Standard_ND6s, Standard_ND12s, Standard_ND24s

The KAgent installer contains the rest of the currently supported set of instance types.

Note

Azure will automatically determine the the best storage depending on the type of instance provisioned
GCP

With GCP, regions control the types of GPUs available rather than the instance type itself. Because of this limitation, Kinetica recommends the following regions (if possible):

  • asia-east1-a, asia-east1-c
  • asia-northeast1-a, asia-northeast1-c
  • asia-northeast3-b, asia-northeast3-c
  • asia-south1-a, asia-south1-b
  • asia-southeast1-b, asia-southeast1-c
  • australia-southeast1-a, australia-southeast1-b australia-southeast1-c
  • europe-west1-b, europe-west1-d
  • europe-west2-a, europe-west2-b
  • europe-west3-b
  • europe-west4-a, europe-west4-b, europe-west4-c
  • northamerica-northeasteast1-a, northamerica-northeasteast1-b, northamerica-northeasteast1-c,
  • southamerica-east1-c
  • us-central1-a, us-central1-b, us-central1-c, us-central1-f
  • us-east1-b, us-east1-c, us-east1-d
  • us-east4-a, us-east4-b, us-east4-c
  • us-west1-a, us-west1-b
  • us-west2-b, us-west2-c

The KAgent installer contains the rest of the currently supported set of regions.

Kinetica's preferred GPUs can be attached to any of the following instances:

  • n1-standard-64
  • n1-highmem-32, n1-highmem-64
  • n1-ultramem-40

The KAgent installer contains the rest of the currently supported set of instance types.

Default Security

VMs will be provisioned in the cloud with the most restrictive security possible.

Port security is configured as follows.

Ports Protocol Source Description
All All Intra-cluster Internal node traffic
22 TCP Internet SSH
8070 TCP Internet AAW UI
8080-8082 TCP Internet GAdmin, KAgent, Security Proxy
8088 TCP Internet Reveal
8443-8444 TCP Internet GAdmin (HTTPS), Reveal (HTTPS)
9049 TCP Internet etcd
9080 TCP Internet Loki
9089-9091 TCP Internet Alert Manager, Grafana, Prometheus
9191-9291 TCP Internet Database API
9300 TCP Internet Host Manager

Provider-specific rules are as follows:

  • AWS
    • Allow external access to external ports
    • Allow access to internal ports within the same security group
  • Azure
    • Allow external access to external ports
    • Allow access to internal ports within the same VPC
  • AWS
    • Allow external access to external ports
    • Allow access to internal ports within the same security group