EC2 instances
Cloudera provisions EC2 instances as part of environment creation process (for Data Lake and FreeIPA) and for compute clusters.
Therefore, you should verify the limits on the number and type of EC2 instances in your AWS account to ensure that you are able to provision an environment and create clusters in Cloudera DataFlow.
Cloudera supports Amazon EC2 reserved instances; That is, If you have purchased reserved instances, Cloudera uses them automatically according to AWS policy.
For a list of supported EC2 instance types, refer to Cloudera Public Cloud service rates.
EC2 instances for Cloudera Data Warehouse clusters
On AWS, you can access EC2 instance metadata for your Cloudera Data Warehouse cluster from a running instance using only Instance Metadata Service V2 (IMDSv2). Cloudera provisions instances for a Cloudera Data Warehouse cluster with IMDSv2. Cloudera no longer supports IMDSv1 for Cloudera Data Warehouse. Cloudera has removed the capability to access IMDSv1 for a Cloudera Data Warehouse cluster in Cloudera.
ECS instances for Cloudera Data Hub and other clusters
On AWS, you can access EC2 instance metadata for Cloudera Data Hub and clusters other than Cloudera Data Warehouse from a running instance using IMDSv1 or IMDSv2. Cloudera supports IMDSv1 but does not support IMDSv2 for these clusters, so you should not enable IMDSv2 alone for any EC2 instances used by Cloudera. For information about configuring IMDS, refer to Configuring the instance metadata service.
Custom images
By default Cloudera provides a set of default images that are used for all provisioned VMs, but you can optionally use custom images for Data Lake, FreeIPA, and Cloudera Data Hub.
You might require a custom image for compliance or security reasons (a “hardened” image), or to have your own packages pre-installed on the image, for example monitoring tools or software.
If you would like to use custom images instead of the default images, refer to Custom images and image catalogs.
