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.

  4. Subscription to Hortonworks Data Cloud AWS Marketplace products: To launch Hortonworks Data Cloud for AWS, you must subscribe to the two AWS Marketplace products: Hortonworks Data Cloud - Controller Service (allows you to launch the cloud controller) and Hortonworks Data Cloud - HDP Services (allows the cloud controller to create HDP clusters). Refer to Subscribe documentation.

Launching the Cloud Controller

  1. Navigate to the Hortonworks Data Cloud - Controller Service AWS Marketplace product listing.

    • For Software Pricing, select your preferred subscription term.
    • For Region, select the region that you want to launch in.
    • For Version, select "1.16.2".
    • For Deployment Options, select the deployment option:
      • BASIC - Cloud Controller with new VPC: This option will launch the cloud controller into a new VPC and use an embedded database for controller metadata. This is the quickest method for launching a cloud controller instance.
      • ADVANCED - Cloud Controller with existing VPC and RDS: This option will launch the cloud controller into an existing VPC and use an existing RDS instance for controller metadata. This is the preferred method for launching a production-ready cloud controller instance.

        The ADVANCED CloudFormation template requires that you provide information about an existing VPC and an existing Amazon RDS instance (PostgreSQL). You must configure a VPC and an Amazon RDS instance first if you plan to use this deployment option. See Advanced Launch Options for more information.

  2. Click Launch with CloudFormation Console.

  3. 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. Enter the Stack name. The Stack name must be unique in your AWS environment.

  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:
    • will allow access from through
    • will allow access from all.
    Refer to Network Security for more information on the inbound ports that are used with the cloud controller.

    SmartSense Configuration

    Parameter Description
    SmartSenseID If you have a SmartSenseID, enter it here. This ID is required to enable support for Flex Subscriptions. You must also opt in for SmartSense telemetry by selecting "I have read and opt in to SmartSense telemetry" in the Telemetry Opt In field.
    Telemetry Opt In SmartSense provides product telemetry and usage information. Refer to SmartSense for more information.
  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.
    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.


  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.


  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 SSH access from the Outputs:

  2. Once the stack creation is complete, browse instance created at the CloudURL provided in the Outputs 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:

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

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