Image

Custom AMI's provide a way to customize the cluster. See Image section.

Head Node

SSH Key allows you to securely connect to the cluster. See more.
Remote-Desktop into the headnode to visualize results. Runs on port 8443.

Compute Queues

Queue 1

Only for p4d.24xlarge, See GdrSupport.

Queue 2

Only for p4d.24xlarge, See GdrSupport.

Queue 3

Only for p4d.24xlarge, See GdrSupport.

Queue 4

Only for p4d.24xlarge, See GdrSupport.

Queue 5

Only for p4d.24xlarge, See GdrSupport.

Queue 6

Only for p4d.24xlarge, See GdrSupport.

Queue 7

Only for p4d.24xlarge, See GdrSupport.

Queue 8

Only for p4d.24xlarge, See GdrSupport.

Queue 9

Only for p4d.24xlarge, See GdrSupport.

Queue 10

Only for p4d.24xlarge, See GdrSupport.

Networking

Storage

Where to mount the filesystem on both Head and Compute Instances.
Specify an existing fileystem and mount it to all instances in the cluster. See FSx Filesystem ID, EFS Filesystem ID, EBS Volume ID
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 workloads and encryption of data in transit. See DeploymentType.
Describes the amount of read and write throughput for each 1 tebibyte of storage, in MB/s/TiB. See PerUnitStorageThroughput.
Set Import/Export Path to read and write files into your filesystem from an S3 bucket. See ExportPath and ImportPath.
When data compression is enabled, Amazon FSx for Lustre automatically compresses newly written files before they are written to disk and automatically uncompresses them when they are read. See DataCompressionType.
Specifies a custom AWS KMS key to use for encryption. See EFS Encryption.
Defines the provisioned throughput (from 1-1024 in MiB/s) of the Amazon EFS file system. If not provided filesystem will be created in 'bursting' mode. See ThroughputMode section.
Specifies if the volume is encrypted. If Encrypted you can optionally specify a KMS Key. See EBS Encryption.
Specifies the Amazon EBS snapshot ID if you're using a snapshot as the source for the volume. See SnapshotID.
Specifies whether the volume should be retained, deleted, or snapshotted when the cluster is deleted. See DeletionPolicy.

Deploy Cluster

Step 1: Download Config

Configure your cluster using the options on the left then download config.

Step 2: Create the Cluster

Run the pcluster cli to create the cluster. To install the CLI run "pip install aws-parallelcluster".

Generated AWS ParallelCluster Config