Cloudera EDH on AWS
Cloudera EDH Quick Start

Storage Configuration

Some EC2 instance types use only instance stores, which are attached to an instance and provide temporary block-level storage. The size of an instance store ranges from 4 GiB to up to 48 TiB, and varies by instance type according to the following table.

Instance type Instance store volumes
c3.4xlarge 2 x 160 GiB SSD (320 GiB)
c3.8xlarge 2 x 320 GiB SSD (640 GiB)
d2.xlarge 2 x 2,000 GiB HDD (6 TiB)
d2.2xlarge 6 x 2,000 GiB HDD (12 TiB)
d2.4xlarge 12 x 2,000 GiB HDD (24 TiB)
i2.xlarge 1 x 800 GiB SSD (800 GiB)
i2.2xlarge 2 x 800 GiB SSD (1,600 GiB)

Instance store volumes are usable only from a single instance during its lifetime; they can't be detached and then attached to another instance. However, they persist during restarts. Since these are local stores, they carry performance benefits during I/O operations, because data doesn't have to be shipped over the network. For more information about instance stores, see the Amazon EC2 documentation.

Other EC2 instance types use EBS volumes, which can be attached and detached from an instance as persistent block-level storage. These are non-local storage devices that may not perform as well as instance stores, but provide additional assurance against data loss, beyond HDFS replication.

Cloudera Director supports using either all instance stores or all EBS volumes for any instance. You can configure an instance template in Cloudera Director to attach additional EBS volumes if you need more space than the default provided by the AMI. See the Cloudera documentation for more information on how to use EBS volumes with Cloudera Manager and Cloudera's Enterprise Data Hub.

Cloudera Manager automatically configures HDFS with datanode directories that are most appropriate for holding HDFS data. See the Cloudera documentation for details on how this automatic configuration process works. In most cases, you do not have to explicitly configure which directories to use.