Creates a new kdb cluster.
See https://www.paws-r-sdk.com/docs/finspace_create_kx_cluster/ for full documentation.
finspace_create_kx_cluster(
clientToken = NULL,
environmentId,
clusterName,
clusterType,
tickerplantLogConfiguration = NULL,
databases = NULL,
cacheStorageConfigurations = NULL,
autoScalingConfiguration = NULL,
clusterDescription = NULL,
capacityConfiguration = NULL,
releaseLabel,
vpcConfiguration,
initializationScript = NULL,
commandLineArguments = NULL,
code = NULL,
executionRole = NULL,
savedownStorageConfiguration = NULL,
azMode,
availabilityZoneId = NULL,
tags = NULL,
scalingGroupConfiguration = NULL
)A token that ensures idempotency. This token expires in 10 minutes.
[required] A unique identifier for the kdb environment.
[required] A unique name for the cluster that you want to create.
[required] Specifies the type of KDB database that is being created. The following types are available:
HDB – A Historical Database. The data is only accessible with read-only permissions from one of the FinSpace managed kdb databases mounted to the cluster.
RDB – A Realtime Database. This type of database captures all the
data from a ticker plant and stores it in memory until the end of
day, after which it writes all of its data to a disk and reloads the
HDB. This cluster type requires local storage for temporary storage
of data during the savedown process. If you specify this field in
your request, you must provide the savedownStorageConfiguration
parameter.
GATEWAY – A gateway cluster allows you to access data across processes in kdb systems. It allows you to create your own routing logic using the initialization scripts and custom code. This type of cluster does not require a writable local storage.
GP – A general purpose cluster allows you to quickly iterate on code
during development by granting greater access to system commands and
enabling a fast reload of custom code. This cluster type can
optionally mount databases including cache and savedown storage. For
this cluster type, the node count is fixed at 1. It does not support
autoscaling and supports only SINGLE AZ mode.
Tickerplant – A tickerplant cluster allows you to subscribe to feed handlers based on IAM permissions. It can publish to RDBs, other Tickerplants, and real-time subscribers (RTS). Tickerplants can persist messages to log, which is readable by any RDB environment. It supports only single-node that is only one kdb process.
A configuration to store Tickerplant logs. It consists of a list of
volumes that will be mounted to your cluster. For the cluster type
Tickerplant, the location of the TP volume on the cluster will be
available by using the global variable .aws.tp_log_path.
A list of databases that will be available for querying.
The configurations for a read only cache storage associated with a cluster. This cache will be stored as an FSx Lustre that reads from the S3 store.
The configuration based on which FinSpace will scale in or scale out nodes in your cluster.
A description of the cluster.
A structure for the metadata of a cluster. It includes information like the CPUs needed, memory of instances, and number of instances.
[required] The version of FinSpace managed kdb to run.
[required] Configuration details about the network where the Privatelink endpoint of the cluster resides.
Specifies a Q program that will be run at launch of a cluster. It is a
relative path within .zip file that contains the custom code, which
will be loaded on the cluster. It must include the file name itself. For
example, somedir/init.q.
Defines the key-value pairs to make them available inside the cluster.
The details of the custom code that you want to use inside a cluster when analyzing a data. It consists of the S3 source bucket, location, S3 object version, and the relative path from where the custom code is loaded into the cluster.
An IAM role that defines a set of permissions associated with a cluster. These permissions are assumed when a cluster attempts to access another cluster.
The size and type of the temporary storage that is used to hold data
during the savedown process. This parameter is required when you choose
clusterType as RDB. All the data written to this storage space is lost
when the cluster node is restarted.
[required] The number of availability zones you want to assign per cluster. This can be one of the following
SINGLE – Assigns one availability zone per cluster.
MULTI – Assigns all the availability zones per cluster.
The availability zone identifiers for the requested regions.
A list of key-value pairs to label the cluster. You can add up to 50 tags to a cluster.
The structure that stores the configuration details of a scaling group.