Provisioning Kinetica in AWS

EC2 Quotas for CPU-Based Clusters

EC2 Quotas for GPU-Based Clusters

Kinetica Pay As You Go (PAYG)

With this offer, Kinetica license fees are based on your hourly usage and the size of the cluster. See Specify Stack Details for specifics on cluster sizes, hardware configurations, and hourly license fees.

To find the Kinetica Pay As You Go (PAYG) Offer, you can search for Kinetica under Discover Products in the AWS Marketplace:

• Pay As You Go Marketplace Listing

  

Kinetica Bring Your Own License (BYOL)

For customers with an existing Kinetica license, you can choose this option and input your existing Kinetica license key. You will not incur additional Kinetica license charges, although you will be charged for AWS infrastructure costs. See Hardware Configuration for more details on the AWS infrastructure provisioned with each cluster configuration.

To find the Kinetica Bring Your Own License (BYOL) Offer, you can search for Kinetica (Bring Your Own License) under Discover Products in the AWS Marketplace:

• Bring Your Own License Marketplace Listing

  

Kinetica Cluster Parameters

• Kinetica Cluster Name: A unique name for your Kinetica cluster
• Kinetica Cluster Size: This setting will determine the performance of your database. Each increase in size roughly corresponds to a doubling in performance. For Kinetica PAYG, license fees are based on the size of the cluster and your hourly usage. See Hardware Configuration below for sizing comparisons and pricing details.
• GPU Acceleration: GPU Acceleration will use GPUs to improve the performance of your database. This option is recommended if you have use cases that would benefit from GPU performance, such as interactive visualization of large scale geographic data or high-cardinality joins. See Hardware Configuration below for GPU vs. non-GPU comparisons.
• Kinetica License Key (Kinetica BYOL only): Your Kinetica license key. Contact Kinetica (sales@kinetica.com) if you need a key.

Kinetica User Information

• Administrator Username: The administrator username that will be used for this cluster
• Administrator Password: The administrator password that will be used to authenticate to this cluster
• Contact First Name: First name of the primary contact for the Kinetica cluster (used by Kinetica support staff only)
• Contact Last Name: Last name of the primary contact for the Kinetica cluster (used by Kinetica support staff only)
• Contact Email Address: Email address of the primary contact for the Kinetica cluster (used by Kinetica support staff only)

Kinetica Networking

• VPC CIDR: This CloudFormation stack will create a new VPC. If you intend to peer this VPC with an existing VPC, choose a CIDR range that does not overlap with the addresses in the existing VPC.

Once you have specified the stack details, click Next.

Troubleshooting Deployment Issues

When the application has successfully provisioned, you should see the CREATE_COMPLETE status for the original CloudFormation stack and all of the nested stacks:

If you see error messages in the original stack or any of the nested stacks, provisioning Kinetica in AWS was not successful. Check the error messages for details on the specific issue. The most common issues for provisioning failures include:

• Insufficient AWS privileges. See AWS Permissions for details on required permissions.

• Insufficient AWS Service Quota in the target AWS region. See AWS Service Quota for details on required service quota.

• Timeout provisioning SSL certificate. Occasionally, the request for an SSL certificate may timeout. If you see the following error message, delete the stack and provision again:

  The following resource(s) failed to create: [certificateStatusCheckerCR].
  

If you experience any other issues, contact Kinetica Support.

Troubleshooting Issues Using Kinetica

If you experience issues using Kinetica to ingest, query, or egress data, check the logs in AWS CloudFormation for details. See Logging in AWS for detailed instructions.

If you have questions about your specific issue, contact Kinetica Support.

Kinetica License Fee

If you are using the Kinetica Pay As You Go offer (PAYG), the Kinetica license fee is based on the size of the Kinetica cluster and the hours of usage. If you suspend Kinetica (manually or through auto suspend), the cluster is suspended and you will not incur Kinetica license fees until the cluster is resumed. For details on the hourly license fees for different cluster sizes, see Hardware Configuration.

If you are using the Kinetica Bring Your Own License offer (BYOL), you will not be charged in AWS for a Kinetica license fee. Your Kinetica license fee has already been paid for outside the AWS Marketplace.

AWS Infrastructure Costs

Your AWS infrastructure costs will depend on the size of the Kinetica cluster, any discounted pricing you may receive (e.g., credits for EC2 Reserved Instances), and your overall usage of the cluster.

The primary cost components will be the EC2 instance(s) and EBS volume(s) used in the EKS cluster to power the Kinetica database and the EC2 instances used for additional cluster infrastructure services (e.g., Kinetica Workbench). When the Kinetica cluster is suspended, the EC2 instance(s) and EBS volume(s) used by the Kinetica database will be spun down and will not incur costs. However, the infrastructure services will continue to run and incur costs.

Finally, your usage of the cluster will also affect the overall cost, although the incremental costs should be minor. For instance, ingesting large volumes of data may increase your network charges while increased usage may increase the log volume stored in CloudWatch.

Below are the estimated costs to operate Kinetica clusters in AWS, assuming on-demand EC2 instance pricing. With EC2 Reserved Instances (especially for the compute nodes), you will be able to realize significant cost savings.