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 |
The KAgent installer contains the rest of the currently supported set of regions. |
The KAgent installer contains the rest of the currently supported set of instance types. |
|
Azure |
The KAgent installer contains the rest of the currently supported set of regions. |
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):
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:
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