Launching an EC2 Instance for Cloudera Director

On AWS, Cloudera Director requires a dedicated Amazon EC2 instance in the same subnet that can access new instances on the private network.

To create the instance, follow these steps:

1. In the AWS Management Console, select EC2 from the Services navigation list box in the desired region.
2. Click the Launch Instance button in the Create Instance section of the EC2 dashboard.
3. Select the AMI for your Cloudera Director instance. Cloudera recommends that you choose from the Community AMIs list and the latest release of the desired supported distribution. See Supported Software and Distributions.
   1. Select Community AMIs in the left pane.
   2. In the search box, type the desired operating system. For example, if you type rhel-6.6 HVM, the search results show the versions of RHEL v6.6 that support HVM. Select the highest GA number to use the latest release of RHEL v6.6 supporting HVM.

      
      

      
      
      

   3. Click Select for the AMI version you choose.
4. Select the instance type for Cloudera Director. Cloudera recommends using c3.large or c4.large instances.
5. Click Next: Configure Instance Details.
   1. Select the correct VPC and subnet.
   2. The cluster launcher requires Internet access; from the Auto-assign Public IP list box, select Enable.
   3. Use the default shutdown behavior, Stop.
   4. Click the Protect against accidental termination checkbox.
   5. (Optional) Click the IAM role drop-down list and select an IAM role.
6. Click Next: Add Storage. Cloudera Director requires a minimum of 8 GB.
7. Click Next: Tag Instance. For the Name key, enter a name for the instance in the Value field. Optionally, click Create Tag to create additional tags for the instance (up to a maximum of 10 tags).

   
   

   
   
   

8. Click Next: Configure Security Group.
9. On the Configure Security Group page, create a new security group or add ports to an existing group. (If you already have a security group with the required ports for Cloudera Director, you can skip this step.)
   1. Select either Create a new security group or Select an existing security group. If you create a new group, enter a Security group name and Description. To edit an existing group, select the group you want to edit.
   2. Click the Type drop-down list, and select a protocol type. Type the port number in the Port Range field.
   3. For each additional port needed, click the Add Rule button. Then click the Type drop-down list, select a protocol type, and type the port number in the Port Range field.

      The following ports must be open for the Cloudera Director EC2 instance:

      Type	Protocol	Port Range	Source
      SSH (22)	TCP (6)	22	0.0.0.0/0
      ALL Traffic	ALL	ALL	security_group_id

10. Click Review and Launch. Scroll down to review the AMI details, instance type, and security group information, and then click Launch.
11. At the prompt for a key pair:
    1. Select Choose an existing key pair and select the key pair you created in Setting up the AWS Environment.
    2. Click the check box to acknowledge that you have access to the private key.
    
    
    
    
    
12. Click Launch Instances.
13. After the instance is created, note its public and private IP addresses.

You are now ready to configure a SOCKS proxy.