Cloudera EDH on AWS
Cloudera EDH Quick Start

Step 2. Launch the Quick Start

In this step, you will launch an AWS CloudFormation template that automates the following:

  • Configures the VPC that provides the base AWS network infrastructure for your EDH deployment.

  • Creates the network resources needed for EDH deployment, including public and private subnets within the VPC, a NAT gateway launched within the public subnet, security groups, and an IAM role.

  • Starts an EC2 instance running Linux (Red Hat) in the public subnet. This instance serves as a launcher node for the Cloudera cluster, and initiates cluster deployment.

  • Downloads Cloudera Director along with the necessary scripts and configuration files. Cloudera Director is used to configure the EDH cluster.

All the steps are fully automated by AWS CloudFormation. The template that deploys Cloudera EDH into an existing VPC skips the VPC and network configuration steps.

Note

Starting with version 1.5.1, Cloudera Director supports key pairs that are generated on the fly. The previous deployment model involved passing the key pair used during launch to the cluster launcher node. In the current deployment model, a key pair is generated dynamically on the cluster launcher node via AWS Command Line Interface (AWS CLI) and is used to launch the EDH cluster.

  1. Choose one of the following options to launch the AWS CloudFormation template into your AWS account. For help choosing an option, see Deployment Scenarios earlier in this guide.

    Option 1

    Deploy Cloudera EDH into a new VPC on AWS

    
                                                Quick Start launch button for Cloudera EDH in new VPC

    Option 2

    Deploy Cloudera EDH into an existing VPC

    
                                                Quick Start launch button for Cloudera EDH in existing VPC

    The template is launched in the US West (Oregon) Region by default. You can change the region by using the region selector in the navigation bar.

    This stack takes approximately 30 minutes to create.

    Note

    You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start. Prices are subject to change. See the pricing pages for each AWS service you will be using in this Quick Start for full details.

  2. On the Select Template page, keep the default URL for the AWS CloudFormation template source, and then choose Next.

  3. On the Specify Details page, review the parameters for the template. Provide values for the parameters that require your input. You can also customize the remaining parameter values. The AWS CloudFormation template uses these to generate a cluster configuration file. When you're done, choose Next.

    In the following tables, parameters are listed by category and described separately for the two deployment options:

    Option 1: Parameters for deploying Cloudera EDH into a new VPC

    View template

    Network Configuration:

    Parameter label Parameter name Default Description
    Availability Zones AvailabilityZones Requires input Availability Zones for the subnets where the cluster launcher node will be deployed. The Quick Start uses two Availability Zones and preserves the logical order you specify.
    VPC CIDR VPCCIDR 10.0.0.0/16 CIDR block for the VPC to create.
    Private Subnet 1 CIDR PrivateSubnet1CIDR 10.0.0.0/19 CIDR block for private subnet 1 located in Availability Zone 1.
    Private Subnet 2 CIDR PrivateSubnet2CIDR 10.0.32.0/19 CIDR block for private subnet 2 located in Availability Zone 2.
    Public Subnet 1 CIDR PublicSubnet1CIDR 10.0.128.0/20 CIDR block for public subnet 1 located in Availability Zone 1.
    Public Subnet 2 CIDR PublicSubnet2CIDR 10.0.144.0/20 CIDR block for public subnet 2 located in Availability Zone 2.
    Permitted IP range RemoteAccessCIDR Requires input CIDR block for SSH access into the EDH launcher instance. We recommend that you set this value to a trusted CIDR block.

    Cloudera Launcher Configuration:

    Parameter label Parameter name Default Description
    Key Name KeyName Requires input An existing public/private key pair, which allows you to connect securely to your instance after it launches. This is the key pair you created in step 1, when you prepared your AWS account.
    Cluster Launcher Instance Type ClusterLauncherType m4.large EC2 instance type for the EDH launcher instance.

    AWS Quick Start Configuration:

    Parameter label Parameter name Default Description
    AWS Quick Start S3 Bucket Name QSS3BucketName aws-quickstart S3 bucket for the Quick Start templates and scripts. You can specify your own bucket if you copy all of the assets and submodules into it, if you want to override the Quick Start behavior for your own implementation. The bucket name can include numbers, lowercase letters, uppercase letters, and hyphens, but should not start or end with a hyphen.
    AWS Quick Start S3 Key Prefix QSS3KeyPrefix quickstart-cloudera/ The S3 key name prefix used to simulate a folder for your copy of Quick Start assets, if you want to override the Quick Start behavior for your own implementation. This prefix can include numbers, lowercase letters, uppercase letters, hyphens, and forward slashes.

    Option 2: Parameters for deploying Cloudera EDH into an existing VPC

    View the template for existing VPC

    Network Configuration:

    Parameter label Parameter name Default Description
    VPC Id VPC Requires input ID of the existing VPC where you want to deploy the Cloudera nodes.
    Private Subnet Id PrivateSubnet Requires input ID of an existing private subnet where Cloudera nodes will be deployed in your VPC.
    Public Subnet Id PublicSubnet Requires input ID of an existing public subnet where the cluster launcher will be deployed in your VPC.
    Public Subnet CIDR PublicSubnet1CIDR Requires input CIDR block of the existing public subnet where the cluster launcher will be deployed in your VPC.
    Private Subnet CIDR PrivSubCIDR Requires input CIDR block of the existing private subnet where Cloudera nodes will be deployed in your VPC.
    Permitted IP range RemoteAccessCIDR Requires input CIDR block for SSH access into the EDH launcher instance. We recommend that you set this value to a trusted CIDR block.

    Cloudera Launcher Configuration:

    Parameter label Parameter name Default Description
    Key Name KeyName Requires input An existing public/private key pair, which allows you to connect securely to your instance after it launches. This is the key pair you created in step 1, when you prepared your AWS account.
    Cluster Launcher Instance Type ClusterLauncherType m4.large EC2 instance type for the EDH launcher instance.

    AWS Quick Start Configuration:

    Parameter label Parameter name Default Description
    AWS Quick Start S3 Bucket Name QSS3BucketName aws-quickstart S3 bucket for the Quick Start templates and scripts. You can specify your own bucket if you copy all of the assets and submodules into it, if you want to override the Quick Start behavior for your own implementation. The bucket name can include numbers, lowercase letters, uppercase letters, and hyphens, but should not start or end with a hyphen.
    AWS Quick Start S3 Key Prefix QSS3KeyPrefix quickstart-cloudera/ The S3 key name prefix used to simulate a folder for your copy of Quick Start assets, if you want to override the Quick Start behavior for your own implementation. This prefix can include numbers, lowercase letters, uppercase letters, hyphens, and forward slashes.

    After the cluster launcher instance is deployed, you can make additional changes to the EDH deployment by using the Cloudera Director server web UI or by modifying the configuration file manually.

  4. On the Options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you're done, choose Next.

  5. On the Review page, review and confirm the settings. Under Capabilities, select the check box to acknowledge that the template will create IAM resources.

  6. Choose Create to deploy the stack.

  7. Monitor the status of the stack. When the status field displays CREATE_COMPLETE and the launcher instance has been created successfully, as shown in Figure 6, you can continue to the next step to configure the cluster.

    
                        Successful creation of launcher instance

    Figure 6: Successful creation of launcher instance