Control Instance Launch

Launching a Control Instance

The following video depicts the Control Instance creation process:

The following steps outline the process to create a Control Instance:

Operating System AMI

  1. Enable the free CentOS base AMI here and then enable CloudyCluster for CentOS in the AWS Marketplace here.

CloudFormation Console

  1. After selecting your Operating System, click the “Launch with CloudFormation Template” button in the Launch section.

  2. On the subsequent “Select Template” screen, click the “Next” button. You do not need to make any changes to the options on this screen before proceeding.

  3. On the next screen, enter a name for your stack.

  4. Select an instance type from the pulldown menu.

  5. Select an existing EC2 Key Pair from the pulldown menu.

  6. Enter a network CIDR representing an address range that is permitted to access the launched instance (i.e., You may enter if you don’t know your address range.

  7. Select your Public Subnet and VPC.

  8. Click the “Next” button.

  9. On the “Options” screen, you can specify tags if you wish. For more information, see Tagging your Amazon EC2 Resources. Then click the “Next” button.

  10. On the “Review” screen, look over the options you have selected and select the check box to acknowledge that the AWS CloudFormation may create IAM resources and incur charges.

  11. Click the “Create” button. Next you will see the creation process underway as your stack is created. You may have to refresh your browser window display to see the new stack in the creation process.

  12. Select the check box next to the new stack with a “CREATE_IN_PROGRESS” status.

  13. Under the list of stack names, select the “Events” tab to view the status of the creation process for your stack.

  14. Select the “Outputs” tab to view the instanceIP address of your new CloudyCluster control instance in the “Value” field.

  15. When the new stack is created, copy the IP address displayed and paste it into a new browser tab. Now you may begin creating your CloudyCluster Environment.