The configuration based on which FinSpace will scale in or scale out nodes in your cluster.

A structure for the metadata of a cluster. It includes information like the CPUs needed, memory of instances, and number of instances.

A list of change request objects.

The structure of the customer code available within the running cluster.

A list of DNS server name and server IP. This is used to set up Route-53 outbound resolvers.

Represents an FinSpace environment.

Provides details in the event of a failed flow, including the error type and the related error message.

Configuration information when authentication mode is FEDERATED.

Defines the ICMP protocol that consists of the ICMP type and code.

The structure containing the metadata of the attached clusters.

The configuration for read only disk cache associated with a cluster.

Details of changeset.

The details of a kdb cluster.

The configuration that allows you to choose how you want to update code on a cluster. Depending on the option you choose, you can reduce the time it takes to update the cluster.

Defines the key-value pairs to make them available inside the cluster.

The structure of database cache configuration that is used for mapping database paths to cache types in clusters.

The configuration of data that is available for querying from this database.

Details about a FinSpace managed kdb database

The active version of the dataview that is currently in use by this cluster.

The structure that stores the configuration details of a dataview.

A collection of kdb dataview entries.

The configuration that contains the database path of the data that you want to place on each selected volume. Each segment must have a unique database path for each volume. If you do not explicitly specify any database path for a volume, they are accessible from the cluster through the default S3/object store segment.

The configuration that allows you to choose how you want to update the databases on a cluster. Depending on the option you choose, you can reduce the time it takes to update the cluster.

The details of a kdb environment.

The structure containing the size and type of the network attached storage (NAS_1) file system volume.

A structure that stores metadata for a kdb node.

The size and type of temporary storage that is used to hold data during the savedown process. All the data written to this storage space is lost when the cluster node is restarted.

A structure for storing metadata of scaling group.

The structure that stores the capacity configuration details of a scaling group.

A structure that stores metadata for a kdb user.

The structure that contains the metadata of the volume.

The network access control list (ACL) is an optional layer of security for your VPC that acts as a firewall for controlling traffic in and out of one or more subnets. The entry is a set of numbered ingress and egress rules that determine whether a packet should be allowed in or out of a subnet associated with the ACL. We process the entries in the ACL according to the rule numbers, in ascending order.

The range of ports the rule applies to.

Configuration information for the superuser.

A configuration to store the 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.

The structure of the transit gateway and network configuration that is used to connect the kdb environment to an internal network.

The structure that consists of name and type of volume.

Configuration details about the network where the Privatelink endpoint of the cluster resides.