Amazon FinSpace pricing

Managed kdb Insights compute can be used for the individual compute nodes in a dedicated cluster or for the hosts in a scaling group. You pay an hourly rate (billed at one-minute resolution), based on the quantity and size of nodes in your dedicated cluster or hosts in your scaling group. Note that only kx.sg* types work with scaling groups.

Note: The price per hour does not include kdb Insights software license. See here for details on kdb licensing.

Data is stored in kdb Databases using change sets. You pay for the amount of data in your database, which is the total of the amount of data you have added to a database via changesets. This is calculated by adding up the GB provisioned for each hour and dividing by the total number of hours in the month, resulting in a “GB-months” value.

Shared storage volumes can be configured to provide POSIX file system storage for writing and storing Tickerplant (TP) logs, writing and storing realtime database (RDB) savedown files, temporary scratch space, and faster database access via Dataviews and high-performance disk cache. You pay for the amount of volume storage configured. This is calculated by adding up the GB provisioned per hour and dividing by the total number of hours in the month, resulting in a "GB-months" value.

When used for cache on a dedicated cluster in a Multi-AZ cluster configuration, a cache in each AZ is automatically created, so your total cost will be 3 times the amount of cache storage you specify for the cluster via the API/Console.

Real-time clusters will persist data from memory to disk so that it can be added to the kdb historical database for historical analytics. For dedicated clusters you can configure separate storage, called Savedown Storage, for each node. For Scaling Groups, you can configure a Storage Volume, which is shared by all nodes in the cluster, to use for savedown storage. 

The amount of savedown storage required will depend on the volume of data your real-time cluster is processing each day. You pay for the amount of storage configured for each node in the cluster. This is calculated by adding up the GB provisioned per hour per active node in the cluster and dividing by the total number of hours in the month, resulting in a "GB-months" value.

Consider a customer that wants to use Managed kdb Insights to support an application with a 10000 GB database, a 1-node Gateway cluster, a 2-node RDB cluster configured with 5000 GB of savedown storage, and a 3 node HDB cluster configured with 2400 GB of 1000 MB/s/TiB High performance cache (which uses a 1000 MB/s/TiB SSD volume). All clusters will use the kx.s.2xlarge node type, and will run 24x7 for the entire month.

Monthly cost calculation (for a 30-day month)

Database Storage: $264

    • 10000 GB x $0.0264 per GB = $264

Gateway: $900

    • 1 node x 720 hours x $1.25 per hour for a kx.s.2xlarge node = $900

RDB: $5,128

    • 2 node x 720 hours x $1.25 per hour for a kx.s.2xlarge node = $1,800
    • 2 nodes x 5000 GB savedown storage each at $0.3328 per month = $3,328

HDB: $7,884

    • 3 nodes x 720 hours x $1.25 per hour for a kx.s.2xlarge node = $2,700
    • 2400 GB 1000 MB/s/TiB cache at $.72 per GB month across 3 replicas, one per AZ = $5,184

Total monthly cost: $14,176

    • $264 (DB) + $900 (Gateway) + $5,128 (RDB) + 7,884 (HDB)