Step 1. Launch the stack

Important

This solution includes an option to send anonymized operational metrics to AWS. We use this data to better understand how customers use this solution and related services and products. AWS owns the data gathered though this survey. Data collection is subject to the AWS Privacy Policy.

To opt out of this feature, download the template, modify the AWS CloudFormation mapping section, and then use the AWS CloudFormation console to upload your template and deploy the solution. For more information, refer to the Collection of operational metrics section in this guide.

This automated AWS CloudFormation template deploys Scale-Out Computing on AWS in the AWS Cloud. Verify that you have completed the prerequisites before you launch the stack.

Note

You are responsible for the cost of the AWS services used while running this solution. Refer to the Cost section for more details. For full details, refer to the pricing webpage for each AWS service you will be using in this solution.

1. Sign in to the AWS Management Console and click the button below to launch the scale-out-computing-on-aws AWS CloudFormation template.

   

   You can also download the template as a starting point for your own implementation.

2. The template launches in the US East (N. Virginia) Region by default. To launch this solution in a different AWS Region, use the Region selector in the console navigation bar. Note that if you choose to launch in a different Region, we recommend using a custom installer in your own Amazon S3 bucket to avoid data transfer costs. For more information, refer to Deployment using custom installer.

   Note

   This solution uses three Availability Zones to maximize the resources users have for submitting jobs. Therefore, you must launch this solution in an AWS Region that has at least three Availability Zones.

   This solution uses the AWS Fargate service, which is currently available in specific AWS Regions only. Therefore, you must deploy this solution in a Region where AWS Fargate is available.

   For more information, refer to Global Infrastructure.

3. On the Create stack page, verify that the correct template URL shows in the Amazon S3 URL text box and choose Next.

4. On the Specify stack details page, assign a name to your solution stack.

   Note

   This solution deploys an analytics stack that limits your stack name to 24 lowercase characters. The template automatically adds the prefix soca- to your solution stack name.

5. Under Parameters, review the parameters for the template and modify them as necessary. This solution uses the following default values.

   Parameter	Default	Description
   Install Location
   Installer S3 Bucket	solutions-reference	The default AWS bucket name. Do not change this parameter unless you are using a custom installer.
   Installer Folder	scale-out-computing-on-aws/latest/	The default AWS folder name. Do not change this parameter unless you are using a custom installer.
   Linux Distribution
   Linux Distribution	AmazonLinux2	Select the preferred Linux distribution for the scheduler and compute instances.
   Custom AMI	<Optional input>	If using a customized Amazon Machine Image, enter the ID. Note If you are using your own AMI, you still have to specify the base Linux Operating System. For more information, refer to Subscribe to Amazon Machine Images.
   Network and Security
   EC2 Instance Type for Scheduler	m5.large	Select the instance type for the scheduler.
   VPC CLuster CIDR	10.0.0.0/16	Choose the CIDR (/16) block for the VPC. This is the internal network over which your cluster will communicate.
   IP Address	<Requires input>	Identifies the default IP(s) allowed to directly SSH into the scheduler and access Amazon ES. To restrict access, use IP/subnet (x.x.x.x/32 for your own IP or x.x.x.x/24 for a range. Replace x.x.x.x with the PUBLIC IP. To identify the public IP, use a tool, such as https://ifconfig.co/. Note 0.0.0.0/0 means ALL INTERNET access and is not recommended.
   Key Pair Name	<Requires input>	Public/private key pair, which allows you to connect securely to your instance after it launches. When you created an AWS account, this is the key pair you created in your preferred region.
   Default LDAP user
   User Name	<Requires input>	The username for your default LDAP user.
   Password	<Requires input>	The password for your default LDAP user. Note 5 characters minimum. Must start with a letter. Accepted special characters include: ! # @ + _ ^ { } [ ] ( )

6. Choose Next.

7. On the Configure Stack Options page, choose Next. Optionally, you can specify tags to associate with the entire stack and specify an IAM role that will be used for all of the stack creation functions.

8. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

9. Choose Create stack to deploy the stack.

   You can view the status of the stack in the AWS CloudFormation console in the Status column. You should see a status of CREATE_COMPLETE in approximately 35 minutes. Note that the custom installer deployment takes approximately 60 minutes.