Exercise 1 - CloudBreak Deployer

Return to Workshop

Login to CloudBreak

Start by going to the link below to open CloudBreak. You’ll use the credentials displayed below. After logging in, you should see the following screen


Login Info

Login: student-0@example.endosys.io
Password: student-YOUR#

A few things to point out

  1. Clusters & Create Cluster - We have a blank Clusters view, and we’ll be making one in a moment
  2. Credentials - You’d normally set up Credentials first, the authentication methods used to connect to your cloud infrastructure. We’ve already done that, though you can click around and see how quickly you can integrate some of your cloud services.
  3. Blueprints - These are Ambari Blueprints, we’ll be using the default ones, specifically the “Data Science Apache Spark 2, Apache Zeppelin” blueprint
  4. Notification Panel - When administering clusters with CloudBreak, this will be an important area to keep watch of. You should see a few things pop up here during the use of this workshop

There are plenty of other features and settings that can be poked around with, but go ahead and click Create Cluster.

General Configuration

  • Select the “cbd-aws” Credential, give the cluster a name maybe something like ds102, and select a region.
    We suggest something in US East for latency and speed benefits, unless you’re physically located in another area that’s closer.
  • The Platform Version should be set to the latest version of HDP, and the Cluster Type should be Data Science: Apache Spark 2, Apache Zeppelin.
  • Once that’s all properly set, click Next.

Hardware and Storage

On the following Hardware and Storage page, make sure all the Instance Counts for the Worker and Compute nodes are set at 4, you’ll need to change the count to 4. This page should look like the screenshot in the below slideshow.

Gateway Configuration

For the Gateway Topology page, for the purposes of this workshop, we’ll add All to the Exposable Services list along side of Ambari.


How to add a rule, see under Master
How to add a rule, see under Master
Completed configuration
Completed configuration
  1. In Step 4, Network, make sure to add access from on port 1-65535 for both TCP and UDP to every Security Group so that the nodes can communicate with each other internally in their subnet.
  2. Then, add a rule to the Master to allow for access to the Zeppelin UI on the Master node. This needs to be for Any source, port 9995, and for both TCP+UDP. Reference the screenshots to the left, there is one with the steps on how to add a rule to the Security Group and one following it showing the completed configuration.


  1. On the final step Security, for our purposes it’s suggested to leave the Cluster User set to admin, set a password to Passw0rd! - you can set it to something else, but we won’t be able to troubleshoot if something goes awry.
  2. Select the Existing SSH public key file that is titled CBDKey-student or else you won’t be able to connect to your cluster.
  3. Once that’s all configured, click Create Cluster. You’ll notice that the cluster is now populated on the Clusters page and has a status of Create in progress. You may also see a stream of notifications coming in at the upper right hand corner.


It will take a few minutes to deploy the cluster so feel free to grab a snack, some swag, or chat with your new friend next to you. Restroom breaks are advised.

Cluster Created

Once your cluster has been created, you’ll see if colored green and in a Running state. Click into it and you should see some of the configuration details and luster Information, an Event History, and some actions you can take on them. Click on the Ambari URL link, and continue into the next exercise.

Workshop Details

Domain Fierce Software Logo
Student ID

Return to Workshop