Launch Cloud Controller

Use the instructions below to launch a cloud controller instance in your AWS environment. Once created, you can use the controller to create, use, and terminate one or more clusters.

Launch Prerequisites

  1. Terms of use: Review the Hortonworks Data Cloud Terms of Use.

  2. AWS account: If you already have an AWS account, log in to the AWS Management Console. Alternatively, you can create a new AWS account.

  3. A key pair in a selected region: The Amazon EC2 instances that you create for Hortonworks Data Cloud will be accessible by the key pair that you provide during installation. Refer to the AWS documentation for instructions on how to create a key pair in a selected region.

Launching the Cloud Controller

  1. Choose one of the deployment options below and click on the link to launch the CloudFormation template that will create the AWS resources, including an EC2 Instance running the cloud controller.

    DEPLOYMENT OPTION #1: BASIC
    Description: Create Cloud Controller EC2 Instance and create a new VPC.
    CloudFormation Template: https://s3.amazonaws.com/hdc-cfn/hdcloud-basic-shared-services-TP-2.0.0.template
    Region Link
    US East (N. Virginia) / us-east-1 Launch the CloudFormation Template in US East
    US West (Oregon) / us-west-2 Launch the CloudFormation Template in US West
    EU Central (Frankfurt) / eu-central-1 Launch the CloudFormation Template in EU Central
    EU West (Dublin) / eu-west-1 Launch the CloudFormation Template in EU West
    Asia Pacific (Tokyo) / ap-northeast-1 Launch the CloudFormation Template in Asia Pacific

    DEPLOYMENT OPTION #2: ADVANCED
    Description: Create Cloud Controller EC2 Instance within an existing VPC and external Amazon RDS instance.
    CloudFormation Template: https://s3.amazonaws.com/hdc-cfn/hdcloud-advanced-shared-services-TP-2.0.0.template
    Region Link
    US East (N. Virginia) / us-east-1 Launch the CloudFormation Template in US East
    US West (Oregon) / us-west-2 Launch the CloudFormation Template in US West
    EU Central (Frankfurt) / eu-central-1 Launch the CloudFormation Template in EU Central
    EU West (Dublin) / eu-west-1 Launch the CloudFormation Template in EU West
    Asia Pacific (Tokyo) / ap-northeast-1 Launch the CloudFormation Template in Asia Pacific

    Important

    The ADVANCED CloudFormation template will use an existing Amazon RDS instance (PostgreSQL DB engine only) for storing cloud controller. You must create your Amazon RDS instance first if you plan to use this deployment option. Refer to Advanced Launch Options for more information.

  2. The Create stack wizard is launched in the Amazon CloudFormation Management Console. The wizard process consists of the following steps:

Select Template

  1. Confirm the Region you want to launch in. To see available regions, refer to AWS Regions.

  2. Click Next to display the Specify Details page.

Specify Details

  1. The default Stack name is HortonworksCloudController.
    The stack name must be unique in your AWS environment, so adjust the name as appropriate if you already have a stack named HortonworksCloudController.

  2. Enter the following Parameters:

    All parameters are required.

    General Configuration

    Parameter Description
    Controller Instance Type EC2 instance type to use for the cloud controller.
    Email Address Username for the Admin login. Must be a valid email address.
    Admin Password Password for Admin login. Must be at least 8 characters containing letters, numbers, and symbols.

    Security Configuration

    Parameter Description
    SSH Key Name Name of an existing EC2 key pair to enable SSH to access the instances. Key pairs are region-specific, so only the key pairs that you created for a selected region will appear in the dropdown. See Launch Prerequisites for more information.
    Remote Access Allow connections to the cloud controller ports from this address range. Must be a valid CIDR IP. For example:
    • 192.168.27.0/24 will allow access from 192.168.27.0 through 192.168.27.255.
    • 192.168.27.10/32 will allow access from 192.168.27.10.
    • 0.0.0.0/0 will allow access from all.
    Refer to Security > Network for more information on the inbound ports that are used with the cloud controller.
  3. If you are launching the cloud controlling using the ADVANCED CloudFormation template the following parameters related to configuring an existing VPC and an external Amazon RDS instance are also displayed:

    All parameters are required.

    Network Configuration

    Parameter Description
    VPC ID Select an existing VPC to deploy the controller inside it.
    Subnet ID Select a subnet from the VPC to use for the controller. Make sure that the subnet is within the VPC selected above.

    RDS Configuration

    Parameter Description
    RDS Endpoint Enter the HOST:PORT of an existing RDS instance (PostgreSQL DB engine).
    RDS Username Username for an existing RDS instance.
    RDS Password Password for an existing RDS instance.
    Database name Name of an existing database in the RDS instance.

    Refer to Advanced Launch Options for more information about Network and Amazon RDS setup.

  4. Click Next to display the Options page.

Options

  1. If you expand the Advanced section, there is an option to Rollback on failure.

    • By default, this option is set to Yes, which means that if there are any event failures when creating the stack, all the AWS resources created so far are deleted (i.e rolled back) to avoid unnecessary charges.
    • If you set this option to No, if there are any event failures when creating the stack, the resources are left intact (i.e. not rolled back). Select the No option to aid in troubleshooting. Note that in this case you are responsible for deleting the stack later.
  2. Click Next to display the Review page.

Review

  1. Click the I acknowledge... checkbox.
  2. Click Create.

The Stack Name is shown in the table with a CREATE_IN_PROGRESS status. You can click on the Stack Name and see the specific events that are in progress. The create process takes about 10 minutes and once ready, you will see CREATE_COMPLETE. If you encounter any failures, refer to the Troubleshooting documentation.

Obtaining the Cloud Controller URL

  1. Once the stack creation is complete, the cloud controller is ready to use. You can obtain the URL to the cloud controller and the SSH access information from the Outputs tab:

    If the Outputs tab is blank, refresh the page.

  2. Once the stack creation is complete, browse instance created at the CloudURL provided in the Outputs tab and log in.

First Time Access and SSL

The cloud controller server has been configured with a self-signed certificate to be accessed via HTTPS. The first time you access the server, your browser will attempt to confirm that the SSL Certificate is valid. Since we are automatically generating a self-signed certificate, your browser will warn you about an Untrusted Connection and ask you to confirm a Security Exception. Depending on your browser, perform the steps below to proceed.

Browser Steps
Firefox Click Advanced > Click Add Exception... > Click Confirm Security Exception
Safari Click Continue
Chrome Click Advanced > Click Proceed...

See Using Your Own SSL Certificate for more information on replacing the self-signed certificate with your own trusted certificate.

Logging In to the Cloud Controller UI

  1. To access the UI of the cloud controller instance that you just launched, browse to the Cloud Controller URL obtained from the CloudFormation's Outputs tab. For example: https://ec2-52-68-242-58.us-west-2.compute.amazonaws.com

  2. Log in using the Email Address and Admin Password provided during the cloud controller launch.

  3. On first login, you will be prompted to accept the Terms of Use to continue.

  4. The cloud controller UI will be displayed. It's time to create a cluster.