You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cft-templates/nextflow-advanced.yaml
+34-12Lines changed: 34 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -57,8 +57,8 @@ Parameters:
57
57
Description: Public Docker container image of the pipeline to be executed. If you are using a custom pipeline, ensure that the custom container image is publicly available on Docker Hub
58
58
InputDataLocation:
59
59
Description: >-
60
-
An S3 bucket which holds input data for the Nextflow pipeline. The bucket name must respect the S3 bucket naming conventions
61
-
(can contain lowercase letters, numbers, periods and hyphens).
60
+
The path to the location which holds the Input data files. This can point to a local path on the head node or to an S3 bucket. Eg /home/ec2-user/studies/ProjectStorage/Shared or mys3bucket.
61
+
Type in the search box to find s3 buckets created through Research Gateway.
62
62
Type: String
63
63
InputDataPattern:
64
64
Description: >-
@@ -67,9 +67,9 @@ Parameters:
67
67
Default: samplesheet.csv
68
68
OutputDataLocation:
69
69
Description: >-
70
-
The full path on the local disk where outputs of the pipeline should be stored. The default path above will enable you to view the outputs via the browser. The path should be accessible to the user ec2-user.
71
-
Alternately, provide an S3 bucket for storing analysis results. The bucket name must respect the S3 bucket naming conventions
72
-
(can contain lowercase letters, numbers, periods and hyphens).
70
+
The path to the location which holds the Output data files. This can point to a local path on the head node or to an S3 bucket.
71
+
A local path should be accessible to the user ec2-user. Alternately, provide an S3 bucket for storing analysis results.
72
+
Type in the search box to find s3 buckets created through Research Gateway.
ConstraintDescription: Must be a valid EC2 instance type.
93
93
KeyPair:
94
-
Description: Name of an existing EC2 KeyPair to enable SSH access to the Head Node. Please create a key pair from the key pair screen if they are not available in the dropdown.
94
+
Description: Name of an existing EC2 KeyPair to enable SSH access to the Head Node. If no key pairs exist, please create one from the button next to the dropdown. Please contact your Administrator if you are unable to create one.
95
95
Type: AWS::EC2::KeyPair::KeyName
96
96
ConstraintDescription: Must be the name of an existing EC2 KeyPair.
0 commit comments