Amazon Elastic Block Store - AWS ParallelCluster

Amazon Elastic Block Store

To use an existing external Amazon EBS volume for long term permanent storage that's independent of the cluster life cycle, specify EbsSettings / VolumeId.

If you don't specify VolumeId, by default, AWS ParallelCluster creates a managed EBS volume from EbsSettings when your cluster is created. AWS ParallelCluster also deletes the volume and data when the cluster is deleted or the volume is removed from the cluster configuration.

For an AWS ParallelCluster managed EBS volume, you can use EbsSettings / DeletionPolicy to instruct AWS ParallelCluster to Delete, Retain, or Snapshot the volume when either the cluster is deleted or when the volume is removed from the cluster configuration. By default, DeletionPolicy is set to Delete.


For AWS ParallelCluster managed shared storage, DeletionPolicy is set to Delete by default.

This means that, if one of the following is true, a managed volume and its data are deleted:

  • You delete the cluster.

  • You change the managed shared storage configuration SharedStorage / Name.

  • You remove the managed shared storage from the configuration.

We recommend that you back up your shared storage with snapshots regularly to avoid the loss of data. For more information about Amazon EBS snapshots, see Amazon EBS snapshots in the Amazon Elastic Compute Cloud User Guide for Linux Instances. To learn how to manage data backups across AWS services, see AWS Backup in the AWS Backup Developer Guide.