SharedStorage section - AWS ParallelCluster

SharedStorage section

(Optional) The shared storage settings for the cluster.

In the SharedStorage section, you can define existing file systems for long term permanent shared storage solutions that are independent of the cluster lifecycle.

You can also define AWS ParallelCluster managed file systems for short term temporary shared storage. By default, AWS ParallelCluster managed file systems are created and deleted with cluster creation and deletion. If you don't back up data from AWS ParallelCluster managed file systems, your data is deleted when the cluster is deleted.

For more information, see Best practices: moving a cluster to a new AWS ParallelCluster minor or patch version.

To use an existing Amazon EBS volume for long term permanent storage that is independent of the cluster life cycle, specify EbsSettings / VolumeId. If you don't specify VolumeId, AWS ParallelCluster creates the EBS volume from EbsSettings when it creates the cluster and deletes the volume and data when the cluster is deleted. If you use the AWS ParallelCluster managed EBS file system, you can use the EbsSettings / DeletionPolicy to instruct AWS ParallelCluster to retain or snapshot the volume when the cluster is deleted.

To use an existing Amazon Elastic File System and Amazon FSx for Lustre file system for long term permanent storage that is independent of the cluster life cycle, specify EfsSettings / FileSystemId and FsxLustreSettings / FileSystemId. If you don't specify FileSystemId, AWS ParallelCluster creates the file system from EfsSettings and FsxLustreSettings when it creates the cluster and deletes the file system and data when the cluster is deleted.

For FSx for ONTAP and FSx for OpenZFS, you can use FsxOntapSettings / VolumeId and FsxOpenZfsSettings / VolumeId to specify whether AWS ParallelCluster mounts existing shared file storage for your cluster.

Configure cluster SharedStorage to mount existing shared file storage and create new shared file storage according to the quotas listed in the following table.

File storage quota per cluster
File shared storage type Quota created and mounted Quota existing mounted Quota net total

Amazon EBS

5

5

5

RAID

1

0

1

Amazon EFS

1

20

21

Amazon FSx †

1 FSx for Lustre

20

21

† AWS ParallelCluster only supports mounting existing Amazon FSx for NetApp ONTAP and Amazon FSx for OpenZFS systems. It doesn't support the creation of new FSx for ONTAP and FSx for OpenZFS systems.

Note

If AWS Batch is used as a scheduler, FSx for Lustre is only available on the cluster head node.

SharedStorage: - MountDir: string Name: string StorageType: Ebs EbsSettings: VolumeType: string Iops: integer Size: integer Encrypted: boolean KmsKeyId: string SnapshotId: string Throughput: integer VolumeId: string DeletionPolicy: string Raid: Type: string NumberOfVolumes: integer - MountDir: string Name: string StorageType: Efs EfsSettings: ThroughputMode: string ProvisionedThroughput: integer Encrypted: boolean KmsKeyId: string PerformanceMode: string FileSystemId: string - MountDir: string Name: string StorageType: FsxLustre FsxLustreSettings: StorageCapacity: integer DeploymentType: string ImportedFileChunkSize: integer DataCompressionType: string ExportPath: string ImportPath: string WeeklyMaintenanceStartTime: string AutomaticBackupRetentionDays: integer CopyTagsToBackups: boolean DailyAutomaticBackupStartTime: string PerUnitStorageThroughput: integer BackupId: string KmsKeyId: string FileSystemId: string AutoImportPolicy: string DriveCacheType: string StorageType: string - MountDir: string Name: string StorageType: FsxOntap FsxOntapSettings: VolumeId: string - MountDir: string Name: string StorageType: FsxOpenZfs FsxOpenZfsSettings: VolumeId: string

Update policy: If this setting is changed, the update is not allowed.

SharedStorage Properties

MountDir (Required, String)

The path where the shared storage is mounted.

Update policy: If this setting is changed, the update is not allowed.

Name (Required, String)

The name of the shared storage. This name is used when updating the settings.

Update policy: If this setting is changed, the update is not allowed.

StorageType (Required, String)

The type of the shared storage. Supported values are Ebs, Efs, FsxLustre, FsxOntap, and FsxOpenZfs.

Note

If AWS Batch is used as a scheduler, FSx for Lustre is only available on the cluster head node.

Update policy: If this setting is changed, the update is not allowed.

EbsSettings

(Optional) The settings for an Amazon EBS volume.

EbsSettings: VolumeType: string Iops: integer Size: integer Encrypted: boolean KmsKeyId: string SnapshotId: string VolumeId: string Throughput: integer DeletionPolicy: string Raid: Type: string NumberOfVolumes: integer

Update policy: If this setting is changed, the update is not allowed.

EbsSettings Properties

VolumeType (Optional, String)

Specifies the Amazon EBS volume type. Supported values are gp2, gp3, io1, io2, sc1, st1, and standard. The default value is gp3.

For more information, see Amazon EBS volume types in the Amazon EC2 User Guide for Linux Instances.

Update policy: If this setting is changed, the update is not allowed.

Iops (Optional, Integer)

Defines the number of IOPS for io1, io2, and gp3 type volumes.

The default value, supported values, and volume_iops to volume_size ratio varies by VolumeType and Size.

VolumeType = io1

Default Iops = 100

Supported values Iops = 100–64000 †

Maximum volume_iops to volume_size ratio = 50 IOPS per GiB. 5000 IOPS requires a volume_size of at least 100 GiB.

VolumeType = io2

Default Iops = 100

Supported values Iops = 100–64000 (256000 for io2 Block Express volumes) †

Maximum Iops to Size ratio = 500 IOPS per GiB. 5000 IOPS requires a Size of at least 10 GiB.

VolumeType = gp3

Default Iops = 3000

Supported values Iops = 3000–16000

Maximum Iops to Size ratio = 500 IOPS per GiB. 5000 IOPS requires a Size of at least 10 GiB.

† Maximum IOPS is guaranteed only on Instances built on the Nitro System provisioned with more than 32,000 IOPS. Other instances guarantee up to 32,000 IOPS. Older io1 volumes might not reach full performance unless you modify the volume. io2 Block Express volumes support volume_iops values up to 256000 on R5b instance types. For more information, see io2 Block Express volumes in the Amazon EC2 User Guide for Linux Instances.

Update policy: This setting can be changed during an update.

Size (Optional, Integer)

Specifies the volume size in gibibytes (GiB). The default value is 35.

Update policy: If this setting is changed, the update is not allowed.

Encrypted (Optional, Boolean)

Specifies if the volume is encrypted. The default value is true.

Update policy: If this setting is changed, the update is not allowed.

KmsKeyId (Optional, String)

Specifies a custom AWS KMS key to use for encryption. This setting requires that the Encrypted setting is set to true.

Update policy: If this setting is changed, the update is not allowed.

SnapshotId (Optional, String)

Specifies the Amazon EBS snapshot ID if you're using a snapshot as the source for the volume.

Update policy: If this setting is changed, the update is not allowed.

VolumeId (Optional, String)

Specifies the Amazon EBS volume ID. When this is specified for an EbsSettings instance, only the MountDir parameter can also be specified.

Update policy: If this setting is changed, the update is not allowed.

Throughput (Optional, Integer)

The throughput, in MiB/s to provision for a volume, with a maximum of 1,000 MiB/s.

This setting is valid only when VolumeType is gp3. The supported range is 125 to 1000, with a default value of 125.

Update policy: This setting can be changed during an update.

DeletionPolicy (Optional, String)

Specifies whether the volume should be retained, deleted, or snapshotted when the cluster is deleted. The supported values are Delete, Retain, and Snapshot. The default value is Delete.

Update policy: This setting can be changed during an update.

Raid

(Optional) Defines the configuration of a RAID volume.

Raid: Type: string NumberOfVolumes: integer

Update policy: If this setting is changed, the update is not allowed.

Raid Properties

Type (Required, String)

Defines the type of RAID array. Supported values are "0" (striped) and "1" (mirrored).

Update policy: If this setting is changed, the update is not allowed.

NumberOfVolumes (Optional, Integer)

Defines the number of Amazon EBS volumes to use to create the RAID array. The supported range of values is 2-5. The default value (when the Raid setting is defined) is 2.

Update policy: If this setting is changed, the update is not allowed.

EfsSettings

(Optional) The settings for an Amazon EFS file system.

EfsSettings: Encrypted: boolean KmsKeyId: string PerformanceMode: string ThroughputMode: string ProvisionedThroughput: integer FileSystemId: string

Update policy: If this setting is changed, the update is not allowed.

EfsSettings Properties

Encrypted (Optional, Boolean)

Specifies if the Amazon EFS file system is encrypted. The default value is false.

Update policy: If this setting is changed, the update is not allowed.

KmsKeyId (Optional, String)

Specifies a custom AWS KMS key to use for encryption. This setting requires that the Encrypted setting is set to true.

Update policy: If this setting is changed, the update is not allowed.

PerformanceMode (Optional, String)

Specifies the performance mode of the Amazon EFS file system. Supported values are generalPurpose and maxIO. The default value is generalPurpose. For more information, see Performance modes in the Amazon Elastic File System User Guide.

We recommend the generalPurpose performance mode for most file systems.

File systems that use the maxIO performance mode can scale to higher levels of aggregate throughput and operations per second. However, there is a trade-off of slightly higher latencies for most file operations.

Update policy: If this setting is changed, the update is not allowed.

ThroughputMode (Optional, String)

Specifies the throughput mode of the Amazon EFS file system. Supported values are bursting and provisioned. The default value is bursting. When provisioned is used, ProvisionedThroughput must be specified.

Update policy: This setting can be changed during an update.

ProvisionedThroughput (Required when ThroughputMode is provisioned, Integer)

Defines the provisioned throughput (in MiB/s) of the Amazon EFS file system, measured in MiB/s. This corresponds to the ProvisionedThroughputInMibps parameter in the Amazon EFS API Reference.

If you use this parameter, you must set ThroughputMode to provisioned.

The supported range is 1-1024. To request a limit increase, contact AWS Support.

Update policy: This setting can be changed during an update.

FileSystemId (Optional, String)

Defines the Amazon EFS file system ID for an existing file system.

When this is specified, only MountDir can be specified. No other EfsSettings can be specified.

If you set this option, it only supports file systems:

  • That don't have a mount target in the stack's Availability Zone

    OR

  • That do have an existing mount target in the stack's Availability Zone, with inbound and outbound NFS traffic allowed from the HeadNode and ComputeNodes.

    To make sure traffic is allowed between the cluster and file system, you can do one of the following:

    • Configure the security groups of the mount target to allow the traffic to and from the CIDR or prefix list of cluster subnets.

      Note

      AWS ParallelCluster validates that port(s) are open and that the CIDR or prefix list is configured. AWS ParallelCluster doesn't validate the content of CIDR block or prefix list.

    • Set custom security groups for cluster nodes by using SlurmQueues / Networking / SecurityGroups and HeadNode / Networking / SecurityGroups. The custom security groups must be configured to allow traffic between the cluster and the file system.

      Note

      If all cluster nodes use custom security groups, AWS ParallelCluster only validates that the port(s) are open. AWS ParallelCluster doesn't validate that the source and destination are properly configured.

Update policy: If this setting is changed, the update is not allowed.

FsxLustreSettings

Note

You must include FsxLustreSettings if your configuration includes an Amazon FSx file system.

(Optional) The settings for an FSx for Lustre file system.

FsxLustreSettings: StorageCapacity: integer DeploymentType: string ImportedFileChunkSize: integer DataCompressionType: string ExportPath: string ImportPath: string WeeklyMaintenanceStartTime: string AutomaticBackupRetentionDays: integer CopyTagsToBackups: boolean DailyAutomaticBackupStartTime: string PerUnitStorageThroughput: integer BackupId: string # BackupId cannot coexist with some of the fields KmsKeyId: string FileSystemId: string # FileSystemId cannot coexist with other fields AutoImportPolicy: string DriveCacheType: string StorageType: string

Update policy: If this setting is changed, the update is not allowed.

Note

If AWS Batch is used as a scheduler, FSx for Lustre is only available on the cluster head node.

FsxLustreSettings Properties

StorageCapacity (Required, Integer)

Sets the storage capacity of the FSx for Lustre file system, in GiB. StorageCapacity is required if you are creating a new file system. Do not include StorageCapacity if BackupId or FileSystemId is specified.

  • For SCRATCH_2, PERSISTENT_1, and PERSISTENT_2 deployment types, valid values are 1200 GiB, 2400 GiB, and increments of 2400 GiB.

  • For SCRATCH_1 deployment type, valid values are 1200 GiB, 2400 GiB, and increments of 3600 GiB.

Update policy: If this setting is changed, the update is not allowed.

DeploymentType (Optional, String)

Specifies the deployment type of the FSx for Lustre file system. Supported values are SCRATCH_1, SCRATCH_2, PERSISTENT_1, and PERSISTENT_2. The default value is SCRATCH_2.

Choose SCRATCH_1 and SCRATCH_2 deployment types when you need temporary storage and shorter term processing of data. The SCRATCH_2 deployment type provides in transit encryption of data and higher burst throughput capacity than SCRATCH_1.

Choose PERSISTENT_1 deployment type for longer term storage and for throughput focused workloads that aren’t latency-sensitive. PERSISTENT_1 supports encryption of data in transit. It's available in all AWS Regions where FSx for Lustre is available.

Choose PERSISTENT_2 deployment type for longer term storage and for latency sensitive workloads that require the highest levels of IOPS/throughput. PERSISTENT_2 supports SSD storage and offers higher PerUnitStorageThroughput (up to 1000 MB/s/TiB). PERSISTENT_2 is available in a limited number of AWS Regions. For more information about deployment types and the list of AWS Regions where PERSISTENT_2 is available, see File system deployment options for FSx for Lustre in the Amazon FSx for Lustre User Guide.

Encryption of data in transit is automatically enabled when you access SCRATCH_2, PERSISTENT_1, or PERSISTENT_2 deployment type file systems from Amazon EC2 instances that support this feature.

Encryption of data in transit for SCRATCH_2, PERSISTENT_1, and PERSISTENT_2 deployment types is supported when accessed from supported instance types in supported AWS Regions. For more information, see Encrypting data in transit in the Amazon FSx for Lustre User Guide.

Note

Support for the PERSISTENT_2 deployment type was added with AWS ParallelCluster version 3.2.0.

Update policy: If this setting is changed, the update is not allowed.

ImportedFileChunkSize (Optional, Integer)

For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system.

The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

Note

This parameter is not supported for file systems using the PERSISTENT_2 deployment type. Configure data repositories associations as described in Linking your file system to an S3 bucket in the Amazon FSx for Lustre User Guide.

Update policy: If this setting is changed, the update is not allowed.

DataCompressionType (Optional, String)

Sets the data compression configuration for the FSx for Lustre file system. The supported value is LZ4, which indicates that data compression is turned on with the LZ4 algorithm. When DataCompressionType is not specified, data compression is turned off when the file system is created.

For more information, see Lustre data compression.

Update policy: This setting can be changed during an update.

ExportPath (Optional, String)

The path in Amazon S3 where the root of your FSx for Lustre file system is exported. This setting is only supported when the ImportPath parameter is specified. The path must use the same Amazon S3 bucket as specified in ImportPath. You can provide an optional prefix to which new and changed data is to be exported from your FSx for Lustre file system. If an ExportPath value is not provided, FSx for Lustre sets a default export path, s3://import-bucket/FSxLustre[creation-timestamp]. The timestamp is in UTC format, for example s3://import-bucket/FSxLustre20181105T222312Z.

The Amazon S3 export bucket must be the same as the import bucket specified by ImportPath. If you only specify a bucket name, such as s3://import-bucket, you get a 1:1 mapping of file system objects to Amazon S3 bucket objects. This mapping means that the input data in Amazon S3 is overwritten on export. If you provide a custom prefix in the export path, such as s3://import-bucket/[custom-optional-prefix], FSx for Lustre exports the contents of your file system to that export prefix in the Amazon S3 bucket.

Note

This parameter is not supported for file systems using the PERSISTENT_2 deployment type. Configure data repositories associations as described in Linking your file system to an S3 bucket in the Amazon FSx for Lustre User Guide.

Update policy: If this setting is changed, the update is not allowed.

ImportPath (Optional, String)

The path to the Amazon S3 bucket (including the optional prefix) that you're using as the data repository for your FSx for Lustre file system. The root of your FSx for Lustre file system will be mapped to the root of the Amazon S3 bucket you select. An example is s3://import-bucket/optional-prefix. If you specify a prefix after the Amazon S3 bucket name, only object keys with that prefix are loaded into the file system.

Note

This parameter is not supported for file systems using the PERSISTENT_2 deployment type. Configure data repositories associations as described in Linking your file system to an S3 bucket in the Amazon FSx for Lustre User Guide.

Update policy: If this setting is changed, the update is not allowed.

WeeklyMaintenanceStartTime (Optional, String)

The preferred start time to perform weekly maintenance, formatted "d:HH:MM" in the UTC time zone, where d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.Double quote is required for this filed.

Update policy: This setting can be changed during an update.

AutomaticBackupRetentionDays (Optional, Integer)

The number of days to retain automatic backups. Setting this to 0 disables automatic backups. The supported range is 0-90. The default is 0. This setting is only valid for use with PERSISTENT_1 and PERSISTENT_2 deployment types. For more information, see Working with backups in the Amazon FSx for Lustre User Guide.

Update policy: This setting can be changed during an update.

CopyTagsToBackups (Optional, Boolean)

If true, tags for the FSx for Lustre file system should be copied to backups. This value defaults to false. If it's set to true, all tags for the file system are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value. This setting is only valid for use with PERSISTENT_1 and PERSISTENT_2 deployment types.

Update policy: If this setting is changed, the update is not allowed.

DailyAutomaticBackupStartTime (Optional, String)

A recurring daily time, in the formatHH:MM. HH is the zero-padded hour of the day (00-23), and MM is the zero-padded minute of the hour (00-59). For example, 05:00 specifies 5 A.M. daily. This setting is only valid for use with PERSISTENT_1 and PERSISTENT_2 deployment types.

Update policy: This setting can be changed during an update.

PerUnitStorageThroughput (Required for PERSISTENT_1 and PERSISTENT_2 deployment types, Integer)

Describes the amount of read and write throughput for each 1 tebibyte of storage, in MB/s/TiB. File system throughput capacity is calculated by multiplying file system storage capacity (TiB) by the PerUnitStorageThroughput (MB/s/TiB). For a 2.4 TiB file system, provisioning 50 MB/s/TiB of PerUnitStorageThroughput yields 120 MB/s of file system throughput. You pay for the amount of throughput that you provision. This corresponds to the PerUnitStorageThroughput property.

Valid values:

  • PERSISTENT_1 SSD storage: 50, 100, 200 MB/s/TiB.

  • PERSISTENT_1 HDD storage: 12, 40 MB/s/TiB.

  • PERSISTENT_2 SSD storage: 125, 250, 500, 1000 MB/s/TiB.

Update policy: If this setting is changed, the update is not allowed.

BackupId (Optional, String)

Specifies the ID of the backup to use for restoring the FSx for Lustre file system from an existing backup. When the BackupId setting is specified, the AutoImportPolicy, DeploymentType, ExportPath, KmsKeyId, ImportPath, ImportedFileChunkSize, StorageCapacity, and PerUnitStorageThroughput settings must not be specified. These settings are read from the backup. Additionally, the AutoImportPolicy, ExportPath, ImportPath, and ImportedFileChunkSize settings must not be specified. This corresponds to the BackupId property.

Update policy: If this setting is changed, the update is not allowed.

KmsKeyId (Optional, String)

The ID of the AWS Key Management Service (AWS KMS) key used to encrypt the FSx for Lustre file system's data for persistent FSx for Lustre file systems at rest. If not specified, the FSx for Lustre managed key is used. The SCRATCH_1 and SCRATCH_2 FSx for Lustre file systems are always encrypted at rest using FSx for Lustre managed keys. For more information, see Encrypt in the AWS Key Management Service API Reference.

Update policy: If this setting is changed, the update is not allowed.

FileSystemId (Optional, String)

Specifies the id of an existing FSx for Lustre file system.

If this option is specified, only the MountDir and FileSystemId settings in the FsxLustreSettings are used and any other settings in the FsxLustreSettings are ignored.

Note

If AWS Batch scheduler is used, FSx for Lustre is only available on the head node.

The file system must be associated to a security group that allows inbound and outbound TCP traffic through ports [988, 1021, 1022, 1023].

To make sure traffic is allowed between the cluster and file system, you can do one of the following:

  • Configure the security groups of the file system to allow the traffic to and from the CIDR or prefix list of cluster subnets.

    Note

    AWS ParallelCluster validates that port(s) are open and that the CIDR or prefix list is configured. AWS ParallelCluster doesn't validate the content of CIDR block or prefix list.

  • Set custom security groups for cluster nodes by using SlurmQueues / Networking / SecurityGroups and HeadNode / Networking / SecurityGroups. The custom security groups must be configured to allow traffic between the cluster and the file system.

    Note

    If all cluster nodes use custom security groups, AWS ParallelCluster only validates that the port(s) are open. AWS ParallelCluster doesn't validate that the source and destination are properly configured.

Update policy: If this setting is changed, the update is not allowed.

AutoImportPolicy (Optional, String)

When you create your FSx for Lustre file system, your existing Amazon S3 objects appear as file and directory listings. Use this property to choose how FSx for Lustre keeps your file and directory listings up to date as you add or modify objects in your linked Amazon S3 bucket. AutoImportPolicy can have the following values:

  • NEW - Automatic import is on. FSx for Lustre automatically imports directory listings of any new objects added to the linked Amazon S3 bucket that do not currently exist in the FSx for Lustre file system.

  • NEW_CHANGED - Automatic import is on. FSx for Lustre automatically imports file and directory listings of any new objects added to the Amazon S3 bucket and any existing objects that are changed in the Amazon S3 bucket after you choose this option.

  • NEW_CHANGED_DELETED - Automatic import is on. FSx for Lustre automatically imports file and directory listings of any new objects added to the Amazon S3 bucket, any existing objects that are changed in the Amazon S3 bucket, and any objects that were deleted in the Amazon S3 bucket after you choose this option.

    Note

    Support for NEW_CHANGED_DELETED was added in AWS ParallelCluster version 3.1.1.

If AutoImportPolicy is not specified, automatic import is off. FSx for Lustre only updates file and directory listings from the linked Amazon S3 bucket when the file system is created. FSx for Lustre does not update file and directory listings for any new or changed objects after choosing this option.

For more information, see Automatically import updates from your S3 bucket in the Amazon FSx for Lustre User Guide.

Note

This parameter is not supported for file systems using the PERSISTENT_2 deployment type. Configure data repositories associations as described in Linking your file system to an S3 bucket in the Amazon FSx for Lustre User Guide.

Update policy: If this setting is changed, the update is not allowed.

DriveCacheType (Optional, String)

Specifies that the file system has an SSD drive cache. This can only be set if the StorageType setting is set to HDD, and the DeploymentType setting is set to PERSISTENT_1. This corresponds to the DriveCacheType property. For more information, see FSx for Lustre deployment options in the Amazon FSx for Lustre User Guide.

The only valid value is READ. To disable the SSD drive cache, don’t specify the DriveCacheType setting.

Update policy: If this setting is changed, the update is not allowed.

StorageType (Optional, String)

Sets the storage type for the FSx for Lustre file system you're creating. Valid values are SSD and HDD.

  • Set to SSD to use solid state drive storage.

  • Set to HDD to use hard disk drive storage. HDD is supported on PERSISTENT deployment types.

The default value is SSD. For more information, see Storage Type Options in the Amazon FSx for Windows User Guide and Multiple Storage Options in the Amazon FSx for Lustre User Guide.

Update policy: If this setting is changed, the update is not allowed.

FsxOntapSettings

(Optional) The settings for an FSx for ONTAP file system.

FsxOntapSettings: VolumeId: string

FsxOntapSettings Properties

VolumeId (Required, String)

Specifies the volume ID of the existing FSx for ONTAP system.

Note
  • If an AWS Batch scheduler is used, FSx for ONTAP is only available on the head node.

  • If the FSx for ONTAP deployment type is Multi-AZ, make sure the route table of the head node subnet is properly configured.

  • Support for FSx for ONTAP was added in AWS ParallelCluster version 3.2.0.

  • The file system must be associated to a security group that allows inbound and outbound TCP and UDP traffic through ports [111, 635, 2049, 4046].

To make sure traffic is allowed between the cluster and file system, you can do one of the following:

  • Configure the security groups of the file system to allow the traffic to and from the CIDR or prefix list of cluster subnets.

    Note

    AWS ParallelCluster validates that port(s) are open and that the CIDR or prefix list is configured. AWS ParallelCluster doesn't validate the content of CIDR block or prefix list.

  • Set custom security groups for cluster nodes by using SlurmQueues / Networking / SecurityGroups and HeadNode / Networking / SecurityGroups. The custom security groups must be configured to allow traffic between the cluster and the file system.

    Note

    If all cluster nodes use custom security groups, AWS ParallelCluster only validates that the port(s) are open. AWS ParallelCluster doesn't validate that the source and destination are properly configured.

Update policy: If this setting is changed, the update is not allowed.

FsxOpenZfsSettings

(Optional) The settings for a FSx for OpenZFS file system.

FsxOpenZfsSettings: VolumeId: string

Update policy: If this setting is changed, the update is not allowed.

FsxOpenZfsSettings Properties

VolumeId (Required, String)

Specifies the volume ID of the existing FSx for OpenZFS system.

Note
  • If an AWS Batch scheduler is used, FSx for OpenZFS is only available on the head node.

  • Support for FSx for OpenZFS was added in AWS ParallelCluster version 3.2.0.

  • The file system must be associated to a security group that allows inbound and outbound TCP and UDP traffic through ports [111, 2049, 20001, 20002, 20003].

To make sure traffic is allowed between the cluster and file system, you can do one of the following:

  • Configure the security groups of the file system to allow the traffic to and from the CIDR or prefix list of cluster subnets.

    Note

    AWS ParallelCluster validates that port(s) are open and that the CIDR or prefix list is configured. AWS ParallelCluster doesn't validate the content of CIDR block or prefix list.

  • Set custom security groups for cluster nodes by using SlurmQueues / Networking / SecurityGroups and HeadNode / Networking / SecurityGroups. The custom security groups must be configured to allow traffic between the cluster and the file system.

    Note

    If all cluster nodes use custom security groups, AWS ParallelCluster only validates that the port(s) are open. AWS ParallelCluster doesn't validate that the source and destination are properly configured.

Update policy: If this setting is changed, the update is not allowed.