After careful consideration, we decided to end support for Amazon FinSpace, effective October 7, 2026. Amazon FinSpace will no longer accept new customers beginning October 7, 2025. As an existing customer with an Amazon FinSpace environment created before October 7, 2025, you can continue to use the service as normal. After October 7, 2026, you will no longer be able to use Amazon FinSpace. For more information, see [Amazon FinSpace end of support](https://docs.aws.amazon.com/finspace/latest/userguide/amazon-finspace-end-of-support.html). 

# Managed kdb volumes


Volumes are managed storage that resides in your Managed kdb Insights environment and can be associated with clusters for storage of data such as TickerPlant (TP) logs, Real-time Database (RDB) savedown files, and temporary storage on General purpose (GP) type clusters. Volumes can also be used by dataview to store copies of your database of disk for fast access when reading data from a database. You can also use volumes to share data between RDB and Intra-day DB (IDB).

## Volumes for temporary data storage


You can use a Managed kdb volume data storage for your cluster. When creating a TP cluster, you must specify a volume that will hold the TP logs. For an RDB or GP cluster running on a scaling group, you can specify a volume to hold savedown or temporary files. 

Multiple clusters can share a single volume for simplicity as shown in Figure 1, or you can configure multiple volumes and associate them with specific clusters for workload isolation as shown in Figure 2.

![\[A diagram that shows how clusters can share volumes.\]](http://docs.aws.amazon.com/finspace/latest/userguide/images/11-managed-kx/finspace-storage-volumes.png)


## Volumes with dataviews


You can use Managed kdb volumes when you create dataviews. Dataviews store a copy of the data in your database on one or more volumes for fast access. When creating a dataview you can specify one or more volumes to store a portion of your database for faster data access compared to querying the data from the default object store format of the data in the database. For more information about using volumes as part of a dataview, see [Creating a kdb dataview](managing-kdb-dataviews.md#create-kdb-dataview).

## Volume types


Volumes are available in different price or performance characteristics based on your need. Currently FinSpace offers the following three types of volume with three throughput characteristics.
+ 1000 MB/s/TiB –
+ 250 MB/s/TiB
+ 12 MB/s/TiB

## Considerations

+ When you delete a cluster, the data remains on the volume. If you don’t want this delete data before deleting the cluster. 
+ You can access data mounted on a volume from within a cluster from the path `/opt/kx/app/shared/$VOLUME_NAME/$CLUSTER_NAME`.

# Managing kdb volumes


The following sections provide a detailed overview of the operations that you can perform by using Managed kdb volumes.

** **Topics** **
+ [

# Creating a Managed kdb volume
](create-volumes.md)
+ [

# Viewing a Managed kdb volume
](view-volumes.md)
+ [

# Updating a Managed kdb volume
](update-volumes.md)
+ [

# Deleting a Managed kdb volume
](delete-volumes.md)

# Creating a Managed kdb volume


**To create a Managed kdb volume**

1. Sign in to the AWS Management Console and open the Amazon FinSpace console at [https://console.aws.amazon.com/finspace](https://console.aws.amazon.com/finspace/landing).

1. In the left pane, under **Managed kdb Insights**, choose **Kdb environments**.

1. From the kdb environments table, choose the name of the environment.

1. On the environment details page, choose **Volumes** tab.

1. Choose **Create volume**.

1. On the **Create volume** page, enter the volume details and choose the **Volume type**. Currently, FinSpace only supports **NAS\$11** (network attached storage) volume type.

1. Choose the throughput from one of the following types.
   + **SSD\$11000**
   + **SSD\$1250**
   + **HDD\$112**

1. Enter the size for the network attached storage configuration. For storage type **SSD\$11000** and **SSD\$1250** you can select the minimum size as 1200 GB or increments of 2400 GB. For storage type **HDD\$112** you can select the minimum size as 6000 GB or increments of 6000 GB.

1. Choose the availability zone that you want to associate with the volume.

1. (Optional) Add a new tag to assign it to your Managed kdb volume. For more information, see [AWS tags](https://docs.aws.amazon.com/finspace/latest/userguide/create-an-amazon-finspace-environment.html#aws-tags). 
**Note**  
You can only add up to 50 tags to your user.

1. Choose **Create volume**. The volume creation process starts and kdb environment details page opens where you can see the status of volume creation under the **Volumes** tab.

# Viewing a Managed kdb volume


**To view and get details of a Managed kdb volume**

1. Sign in to the AWS Management Console and open the Amazon FinSpace console at [https://console.aws.amazon.com/finspace](https://console.aws.amazon.com/finspace/landing).

1. In the left pane, under **Managed kdb Insights**, choose **Kdb environments**.

1. From the kdb environments table, choose the name of the environment.

1. On the environment details page, choose the **Volumes** tab. The table under this tab displays a list of volumes created in the environment.

1. Choose a volume name to view its details. The volume details page opens where you can view the following details.
   + **Volume details** section – Displays the metadata of the volume that you created.
   + **Configuration** tab – Displays the details about the network attached storage and availability zones.
   + **Monitoring** tab – Displays the dashboard of volume metrics. You can view activity logs for your volume here. 
   + **Clusters** tab – Displays a list of clusters attached to this volume. For information on how to create clusters, see [Creating a Managed kdb Insights cluster](create-kdb-clusters.md).
   + **Tags** tab – Displays a list of key-value pairs associated with the volume. If you did not provide tags during volume creation, choose **Manage tags** to add new tags.

# Updating a Managed kdb volume


You can only edit the description and size of a volume. When you update a volume, you can only increase the volume size but cannot reduce it. During the update process, the filesystem might be unavailable for a few minutes. You can retry any operations after the update is complete. 

**To update a Managed kdb volume**

1. Sign in to the AWS Management Console and open the Amazon FinSpace console at [https://console.aws.amazon.com/finspace](https://console.aws.amazon.com/finspace/landing).

1. In the left pane, under **Managed kdb Insights**, choose **Kdb environments**.

1. From the list of environments, choose a kdb environment.

1. On the environment details page, choose the **Volumes** tab.

1. From the list of clusters, choose the one that you want to edit. The volume details page opens.

1. Choose **Edit** and update the required details.

1. Choose **Save changes**.

# Deleting a Managed kdb volume


**Note**  
This action is irreversible. You cannot delete a volume if it's attached to any cluster or dataview. 

**To delete a Managed kdb volume**

1. Sign in to the AWS Management Console and open the Amazon FinSpace console at [https://console.aws.amazon.com/finspace](https://console.aws.amazon.com/finspace/landing).

1. In the left pane, under **Managed kdb Insights**, choose **Kdb environments**.

1. From the kdb environments table, choose the name of the environment.

1. On the environment details page, choose the **Volumes** tab.

1. From the list of volumes, choose the volume that you want to delete and choose **Delete**. Alternatively, you can choose the volume name and open the volume details page to delete it.

1. On the confirmation dialog box, enter **confirm** to provide a written consent to delete the resource permanently.

1. Choose **Delete**.