Requirements and Supported Versions

Cloud Providers

Cloudera Director has native support for Amazon Web Services (AWS) and Google Cloud Platform.

Each Cloudera Director release embeds the current plug-in for supported cloud providers, but a newer plug-in may have been posted on the Cloudera GitHub site subsequent to the Cloudera Director release. To check for the latest version, click the appropriate link:

Cloudera Director Service Provider Interface (SPI)

The Cloudera Director SPI defines an open source Java interface that plug-ins implement to add support for additional cloud providers to Cloudera Director. For more information, see the file in the SPI Cloudera Director GitHub repository.

Supported Software and Distributions

The table below lists software requirements, recommendations, and supported versions for resources used with Cloudera Director.

  Cloudera Director Cloudera Manager and CDH
Operating Systems (64-bit only)

RHEL and CentOS 6.5, 6.7, 7.1, and 7.2

Ubuntu 14.04

RHEL and CentOS 6.5, 6.7, 7.1, and 7.2
Oracle Java SE Development Kit (JDK) Oracle JDK version 7 or 8

Oracle JDK version 7 or 8

Default Database Embedded H2 database Embedded PostgreSQL Database
Supported Databases

MySQL 5.5, 5.6

MariaDB 5.5

MySQL 5.5, 5.6

MariaDB 5.5

Resource Requirements

The table below lists requirements for resources used with Cloudera Director.

  Cloudera Director Cloudera Manager and CDH
CPU 2 4
RAM 3.75 GB 64 GB
Disk 8 GB 500 GB
Recommended AWS instance c3.large or c4.large

Cloudera Manager: m4.xlarge or m4.4xlarge

Recommended Google Cloud Platform instance n1-standard-2 n1-highmem-4 or n1-highmem-8

Supported Cloudera Manager and CDH Versions

Cloudera Director 2.0 can install any version of Cloudera Manager 5 with any CDH 5 parcels. Use of CDH packages is not supported.

Networking and Security Requirements

Cloudera Director requires the following inbound ports to be open:
  • TCP ports 22: These ports allow SSH to Cloudera Director instance.
  • All traffic across all ports within the security group: This rule allows connectivity with all the components within the Hadoop cluster. This rule avoids numerous individual ports to be opened in the security group.
Type Protocol Port Range Source
SSH (22) TCP (6) 22
ALL Traffic ALL ALL security_group_id

See note paragraph below.

To connect to the AWS network, Cloudera recommends that you open only these ports and set up a SOCKS proxy. Unless your network has direct connection to AWS, you must set this up to access the Cloudera Director instance. This is done in a later step.

Ports Used by Cloudera Director

Cloudera Director uses the ports listed in the table below.
Component Service Port Access Requirement Configuration Comment
Cloudera Director server HTTP/HTTPS port for Cloudera Director UI and API 7189 Must be accessible from outside the cluster server.port in Web UI and API
Cloudera Director internal shell CRaSH shell port 2000 localhost only shell.ssh.port in Used with the ssh client
Cloudera Director also uses the following ports in a typical deployment:
  • 80 and 443: to connect to external services for validation and tracking.
  • 7180: to talk to the Cloudera Manager API
  • 22: to connect to new instances over SSH
  • 123: to configure NTP within the cluster.

Supported Browsers

Cloudera Director supports the following browsers:
  • Mozilla Firefox 11 and higher
  • Google Chrome
  • Internet Explorer 9 and higher
  • Safari 5 and higher