Skip to content

Lab 1: Deploy Environment

Your temporary AWS account has been pre-provisioned with a multiuser computing environment. You'll use this pre-built cluster for the workshop labs.

We also want you to have hands-on experience deploying you're own cluster, and in this module we will have you walk through the process of launching a second cluster in your temporary AWS account. This second cluster will be provisioned in the background while you work on the rest of the workshop in the pre-built cluster.

Step 1: Launch stack

This automated AWS CloudFormation template deploys a scale-out computing environment in the AWS Cloud.

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

    Launch Stack

  2. Verify the launch region is Oregon

    Important

    The template must be launched in Oregon for this workshop.

  3. On the Create stack page, you should see the template URL in the Amazon S3 URL text box and choose Next.

  4. On the Specify stack details page, assign a name to your solution stack. We recommend naming it "mfg405".

    Warning

    The stack name must be less than 20 characters and must be lower-case only.

  5. Under Parameters, modify the the last four parameters, which are marked with REQUIRED. Leave all other fields with their default values. These are variables passed the CloudFormation automation that deploys the environment.

    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 The preferred Linux distribution for the scheduler and compute instances. Do not change this parameter.
    Custom AMI If using a customized Amazon Machine Image, enter the ID. Leave this field blank.
    Network and Security
    EC2 Instance Type for Scheduler node m5.large The instance type for the scheduler. Do not change this parameter.
    VPC Cluster CIDR 110.0.0.0/16 Choose the CIDR (/16) block for the VPC. Do not change this parameter.
    IP Address 0.0.0.0/0 REQUIRED The public-facing IP address that is permitted to log into the environment. You can leave it at default, but we recommend you change it to your public-facing IP address. You can find your public-facing IP address at http://checkip.amazonaws.com. Add the /32 suffix to the IP number.
    Key Pair Name ee-default-keypair REQUIRED Select the ee-default-keypair provided by the workshop.
    Default LDAP User
    User Name REQUIRED Set a username for the default cluster user.
    Password REQUIRED Set a password for the default cluster user. (5 characters minimum, uppercase/lowercase/digit only)
  6. Choose Next.

  7. On the Configure Stack Options page, choose Next.

  8. On the Review page, review the settings and check the two boxes acknowledging that the template will create AWS Identity and Access Management (IAM) resources and might require the CAPABILITY_AUTO_EXPAND capability.

  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.

You can now move on to the next lab. Click Next.