Cloud.Service.AWS.EMR.Cluster
{
"account": "string",
"additional_info": "string",
"applications": [
"string"
],
"autoscaling_role": "string",
"bootstrap_action": [
{
"args": [
"string"
],
"name": "string",
"path": "string"
}
],
"cluster_state": "string",
"configurations": "string",
"configurations_json": "string",
"core_instance_count": 0,
"core_instance_type": "string",
"count": 0,
"custom_ami_id": "string",
"ebs_root_volume_size": 0,
"ec2_attributes": [
{
"additional_master_security_groups": "string",
"additional_slave_security_groups": "string",
"emr_managed_master_security_group": "string",
"emr_managed_slave_security_group": "string",
"instance_profile": "string",
"key_name": "string",
"service_access_security_group": "string",
"subnet_id": "string"
}
],
"instance_group": [
{
"autoscaling_policy": "string",
"bid_price": "string",
"ebs_config": [
{
"iops": 0,
"size": 0,
"type": "string",
"volumes_per_instance": 0
}
],
"id": "string",
"instance_count": 0,
"instance_role": "string",
"instance_type": "string",
"name": "string"
}
],
"keep_job_flow_alive_when_no_steps": false,
"kerberos_attributes": [
{
"ad_domain_join_password": "string",
"ad_domain_join_user": "string",
"cross_realm_trust_principal_password": "string",
"kdc_admin_password": "string",
"realm": "string"
}
],
"log_uri": "string",
"master_instance_type": "string",
"master_public_dns": "string",
"name": "string",
"region": "string",
"release_label": "string",
"scale_down_behavior": "string",
"security_configuration": "string",
"service_role": "string",
"step": [
{
"action_on_failure": "string",
"hadoop_jar_step": [
{
"args": [
"string"
],
"jar": "string",
"main_class": "string"
}
],
"name": "string"
}
],
"termination_protection": false,
"visible_to_all_users": false
}(Required) The name of the AWS cloud account to use for this resource
JSON string for additional features, such as proxy information. There is no API to retrieve this argument value from the provider after EMR cluster creation, so the application cannot detect drift from the actual EMR cluster if its value is changed outside it.
Applications to add to the cluster: Flink, Hadoop, Hive, Mahout, Pig, Spark, and JupyterHub. Multiples allowed. Case insensitive as of EMR 5.14.0.
IAM role that provides permissions that automatic scaling requires in order to launch and terminate EC2 instances in an instance group.
Settings for bootstrap actions to run before Hadoop is started.
State of the EMR cluster: STARTING, BOOTSTRAPPING, RUNNING, WAITING, TERMINATING, TERMINATED, or TERMINATED_WITH_ERRORS.
JSON file used for overriding default configurations for applications. See the AWS EMR documentation about configuring applications.
JSON string for supplying a list of configurations for the EMR cluster.
Total number of Amazon EC2 instances used to execute the job flow. Default is 1. EMR uses one of these nodes as the cluster master node and the remainder as core nodes. Cannot be specified if instance_groups is set.
The EC2 instance type of the slave nodes. Cannot be specified if instance_groups is set.
The number of resource instances to be created.
In EMR 5.7.0 and later, a custom Amazon Linux AMI for the cluster, instead of an EMR-owned AMI.
In EMR 4.x and later, size in gigabytes of the EBS root device volume of the Linux AMI used for each EC2 instance.
Attribute settings for the EC2 instances that are running the job.
A list of instance_group objects for each instance group in the cluster. Exactly one master_instance_type and instance_group must be specified. When instance_group is set, it must contain a configuration block for at least the MASTER instance group type, plus any additional instance groups.
Whether to keep the cluster running when no steps are underway or all steps are complete. Default is on.
Settings for Kerberos configuration of the cluster.
Simple storage service (S3) bucket in which to store job log files.
The EC2 instance type of the master node. Exactly one master_instance_type and instance_group must be specified.
Public DNS name of the master node EC2 instance.
(Required) The name of the entire job flow.
(Required) Target cloud region, such as us-east-1. Must be within the provider cloud account.
(Required) Name of the Amazon EMR version.
The way that individual Amazon EC2 instances terminate when an automatic scale-in activity occurs or an instance group is resized.
The security configuration name to attach to the EMR cluster. Only valid for EMR clusters with release_label of 4.8.0 or later.
(Required) Identity and Access Management (IAM) role that the Amazon EMR service assumes to access AWS resources.
All steps to run when creating the Elastic Map Reduce (EMR) cluster. Use life cycle configuration block with ignore_changes if other steps are being managed outside of the application.
List of tags to apply to the EMR cluster.
Whether to protect the instance from automatic termination. Default is off.
Whether the job flow is visible to all IAM users of the AWS account associated with the job flow. Default is true.