Cloudera EDH on AWS
Cloudera EDH Quick Start

Step 4. Deploy the EDH Cluster

Cloudera Director supports two options for cluster deployment:

  • Option 1 (recommended): You can deploy using the Cloudera Director Server to manage multiple clusters. Cloudera Director provides a simple interface to deploy, scale, and terminate clusters, and helps you manage the cluster.

  • Option 2: You can deploy using the CLI and manage the nodes manually.

Option 1: Deploy Using Cloudera Director Server (Recommended)

The Cloudera Director server deployment provides a web UI to deploy clusters of any topology—simple or complex. By default, this Quick Start automatically installs and starts the Cloudera Director server on port 7189 of the cluster launcher instance, during instance bootstrapping. Once the SSH tunnel is complete from step 3, you can use the browser on your local system and connect to localhost:7189.

After you accept the end user license, log in to Cloudera Director by using the default user name “admin” and password “admin”. The Cloudera Director dashboard is displayed.


                    Cloudera Director dashboard

Figure 9: Cloudera Director dashboard

The Quick Start has already loaded the reference environment into the Cloudera Director server to help you get started. Choose Add Cloudera Manager and select the reference environment from the menu to see the deployment configuration showing up in the web UI, as shown in Figure 10.


                    Adding Cloudera Manager via Cloudera Director Web UI

Figure 10: Adding Cloudera Manager through the Cloudera Director Web UI

Make the following selections to determine how Cloudera Manager will be set up:

  • Provide a name for the Cloudera Manager deployment.

  • Select an instance template based on the instance type desired for the instance that will host the Cloudera Manager installation.

  • Select a license type. If you have a Cloudera Enterprise license, you can enter it now, either directly or by file upload. If you do not have a license, select either the Enterprise Trial or Express option.

  • Choose whether you wish Cloudera Manager to use its embedded database server or an external one, which may either already exist or may be created by Cloudera Director in Amazon RDS.

After you make any necessary modifications to the deployment configuration, choose Continue. Cloudera Director begins launching and configuring a Cloudera Manager instance while presenting the configuration for the EDH cluster.


                    Adding Cloudera cluster nodes

Figure 11: Adding Cloudera cluster nodes

Make the following selections to determine how the EDH cluster will be set up:

  • Provide a name for the cluster.

  • Choose the version of CDH, Cloudera’s Enterprise Data Hub distribution, to install. The default is to use the latest available version of CDH released along with Cloudera Director.

  • Select the variety of services to install in the EDH, from a minimal core set to all available services.

  • Select the number and instance template for the instance groups that Cloudera Director will allocate in Amazon EC2. Each instance in an instance group has the same variety of roles (service components). A minimal cluster should use the given groups with their default roles. Be sure to select the number of workers desired; in all cases, stay above the default minimum count for each instance group.

After you make any necessary modifications to the cluster configuration, choose Continue. Cloudera Director will display progress bars tracking the progress of Cloudera Manager and EDH cluster creation. When progress is complete, your EDH cluster is ready for use.

Option 2: Deploy Using the CLI, No Server

To deploy the EDH cluster, run the cloudera-director executable using one of the configuration files, as follows.

For a simple cluster:

cloudera-director bootstrap aws.simple.conf

For an advanced cluster:

cloudera-director bootstrap aws.reference.conf

Figure 12 shows a typical sequence of a completed EDH deployment using Cloudera Director.


                    EDH deployment sequence

Figure 12: EDH deployment sequence

Cloudera Director also supports other command arguments, such as terminate and status.

For example, for a simple cluster:

cloudera-director status aws.simple.conf

For an advanced cluster:

cloudera-director status aws.reference.conf

                    EDH deployment sequence with status query

Figure 13: EDH deployment sequence with status query