Skip to content

Commit 30d4098

Browse files
committed
Merge branch '69-improve-getting-started-cfn' into 'main'
Resolve "Improve Getting Started Cfn asset descriptions, instructions" Closes #69 See merge request mwvaughn/aws-hpc-recipes!169
2 parents 0bde555 + 36fc854 commit 30d4098

File tree

8 files changed

+40
-274
lines changed

8 files changed

+40
-274
lines changed

recipes/pcs/getting_started/assets/cfn-pcs-lt-efs-fsxl.yaml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
AWSTemplateFormatVersion: 2010-09-09
2-
Description: Launch templates for AWS PCS login and compute node groups, supporting shared EFS and FSx for Lustre file systems
2+
Description: EC2 launch templates for AWS PCS login and compute node groups.
3+
This template creates EC2 launch templates for AWS PCS login and compute node groups.
4+
It demonstrates mounting EFS and FSx for Lustre file systems, configuring EC2 instance tags, enabling Instance Metadata Service Version 2 (IMDSv2), and setting up the cluster security group for communication with the AWS PCS controller.
5+
Additionally, it shows how to configure inbound SSH access to the login nodes.
6+
Use this template as a starting point to create custom launch templates tailored to your specific requirements.
7+
Check the Outputs tab of this stack for useful details about resources created by this template.
38

49
Metadata:
510
AWS::CloudFormation::Interface:

recipes/pcs/getting_started/assets/cluster.yaml

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,11 @@
11
AWSTemplateFormatVersion: '2010-09-09'
22
Transform: AWS::Serverless-2016-10-31
3-
Description: AWS Parallel Computing Service "getting started" cluster
3+
Description: AWS PCS "Getting Started" cluster.
4+
This template deploys a small HPC cluster with 1 login node and up to 4 compute nodes.
5+
It includes an EFS file system for shared storage and an FSx for Lustre file system for high-speed temporary storage.
6+
The cluster is deployed in a new VPC with both public and private subnets.
7+
It can be accessed via the browser using AWS Systems Manager Session Manager or over the internet via SSH.
8+
To access the cluster, check the Outputs tab of this stack for relevant links.
49

510
### Stack metadata
611
Metadata:
@@ -30,7 +35,7 @@ Parameters:
3035
AllowedValues:
3136
- x86
3237
- Graviton
33-
Description: Architecture of the login and compute node instances
38+
Description: Processor architecture for the login and compute node instances
3439

3540
SlurmVersion:
3641
Type: String
@@ -41,12 +46,12 @@ Parameters:
4146
- 24.05
4247

4348
KeyName:
44-
Description: KeyPair to login to the head node
49+
Description: SSH keypair to log in to the head node
4550
Type: AWS::EC2::KeyPair::KeyName
4651
AllowedPattern: ".+" # Required
4752

4853
ClientIpCidr:
49-
Description: IP(s) allowed to directly access the login nodes. We recommend that you restrict it with your own IP/subnet (x.x.x.x/32 for your own ip or x.x.x.x/24 for range. Replace x.x.x.x with your own PUBLIC IP. You can get your public IP using tools such as https://ifconfig.co/)
54+
Description: IP(s) allowed to access the login node over SSH. We recommend that you restrict it with your own IP/subnet (x.x.x.x/32 for your own ip or x.x.x.x/24 for range. Replace x.x.x.x with your own PUBLIC IP. You can get your public IP using tools such as https://ifconfig.co/)
5055
Default: 127.0.0.1/32
5156
Type: String
5257
AllowedPattern: (\d{1,3})\.(\d{1,3})\.(\d{1,3})\.(\d{1,3})/(\d{1,2})

recipes/pcs/getting_started/assets/pcs-cfn.yaml

Lines changed: 0 additions & 264 deletions
This file was deleted.

recipes/pcs/getting_started/assets/pcs-cluster-sg.yaml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
AWSTemplateFormatVersion: 2010-09-09
2-
Description: Security group for communications between AWS PCS controller, compute nodes, and client nodes, plus optional inbound SSH security group.
2+
Description: Security group for AWS PCS clusters.
3+
This template creates a self-referencing security group that enables communications between AWS PCS controller, compute nodes, and client nodes.
4+
Optionally, it can also create a security group to enable SSH access to the cluster.
5+
Check the Outputs tab of this stack for useful details about resources created by this template.
36

47
Metadata:
58
AWS::CloudFormation::Interface:

recipes/pcs/getting_started/assets/pcs-iip-minimal.yaml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
AWSTemplateFormatVersion: 2010-09-09
2-
Description: Minimal IAM instance profile for AWS PCS compute node groups
2+
Description: Minimal IAM instance profile for AWS PCS compute node groups.
3+
This template creates an IAM instance profile with a role that has the minimum required permissions for AWS PCS compute node groups.
4+
Optionally, the profile can be configured to enable the following services on PCS-managed instances:
5+
AWS Systems Manager, Amazon S3 (read-only access), Amazon CloudWatch Agent.
6+
Check the Outputs tab of this stack for useful details about resources created by this template.
37

48
Metadata:
59
AWS::CloudFormation::Interface:

recipes/pcs/getting_started/assets/pcs-lt-efs-fsxl.yaml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
AWSTemplateFormatVersion: 2010-09-09
2-
Description: Launch templates for AWS PCS login and compute node groups, supporting shared EFS and FSx for Lustre file systems
2+
Description: EC2 launch templates for AWS PCS login and compute node groups.
3+
This template creates EC2 launch templates for AWS PCS login and compute node groups.
4+
It demonstrates mounting EFS and FSx for Lustre file systems, configuring EC2 instance tags, enabling Instance Metadata Service Version 2 (IMDSv2), and setting up the cluster security group for communication with the AWS PCS controller.
5+
Additionally, it shows how to configure inbound SSH access to the login nodes.
6+
Use this template as a starting point to create custom launch templates tailored to your specific requirements.
7+
Check the Outputs tab of this stack for useful details about resources created by this template.
38

49
Metadata:
510
AWS::CloudFormation::Interface:

recipes/pcs/getting_started/assets/pcs-lt-efs.yaml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
AWSTemplateFormatVersion: 2010-09-09
2-
Description: Create a launch template to support a PCS compute node group mounting EFS
2+
Description: EC2 launch templates for AWS PCS compute node groups.
3+
This template creates EC2 launch templates for AWS PCS compute node groups.
4+
It demonstrates mounting an EFS file system, configuring EC2 instance tags, enabling Instance Metadata Service Version 2 (IMDSv2), and setting up the cluster security group for communication with the AWS PCS controller.
5+
Use this template as a starting point to create custom launch templates tailored to your specific requirements.
6+
Check the Outputs tab of this stack for useful details about resources created by this template.
37

48
Metadata:
59
AWS::CloudFormation::Interface:

recipes/pcs/getting_started/assets/pcs-lt-simple.yaml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
AWSTemplateFormatVersion: 2010-09-09
2-
Description: Simple launch template for an AWS PCS compute node group
2+
Description: Minimal EC2 launch template for an AWS PCS compute node group.
3+
This template creates a minimal EC2 launch template for AWS PCS compute node groups.
4+
It demonstrates how to configure EC2 instance tags, IMDSv2, and the cluster security group needed to communicate with the AWS PCS controller.
5+
You can use it as a starting point for creating a custom launch template to meet your specific needs.
6+
Check the Outputs tab of this stack for useful details about resources created by this template.
37

48
Metadata:
59
AWS::CloudFormation::Interface:

0 commit comments

Comments
 (0)