Adds an instance fleet to a running cluster.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x.
+ * 4.8.0 and higher, excluding 5.0.x. *Cancels a pending step or steps in a running cluster. Available only in Amazon EMR versions 4.8.0 and later, excluding version 5.0.0. A maximum of 256 steps are allowed in - * each CancelSteps request. CancelSteps is idempotent but asynchronous; it does not guarantee - * that a step will be canceled, even if the request is successfully submitted. When you use - * Amazon EMR releases 5.28.0 and later, you can cancel steps that are in a + *
Cancels a pending step or steps in a running cluster. Available only in Amazon EMR versions 4.8.0 and higher, excluding version 5.0.0. A maximum of 256 steps are allowed
+ * in each CancelSteps request. CancelSteps is idempotent but asynchronous; it does not
+ * guarantee that a step will be canceled, even if the request is successfully submitted. When
+ * you use Amazon EMR releases 5.28.0 and higher, you can cancel steps that are in a
* PENDING or RUNNING state. In earlier versions of Amazon EMR, you can only cancel steps that are in a PENDING state.
Lists all available details about the instance fleets in a cluster.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *A list of the instance types that Amazon EMR supports. You can filter the - * list by Amazon Web Services Region and Amazon EMR release.
+ *A list of the instance types that Amazon EMR supports. You can filter the list + * by Amazon Web Services Region and Amazon EMR release.
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-emr/src/commands/ModifyInstanceFleetCommand.ts b/clients/client-emr/src/commands/ModifyInstanceFleetCommand.ts index a371ac02383b..27bdc9d0655d 100644 --- a/clients/client-emr/src/commands/ModifyInstanceFleetCommand.ts +++ b/clients/client-emr/src/commands/ModifyInstanceFleetCommand.ts @@ -42,7 +42,7 @@ export interface ModifyInstanceFleetCommandOutput extends __MetadataBearer {} * succeeds or fails atomically. *The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *Auto-termination is supported in Amazon EMR releases 5.30.0 and 6.1.0 and - * later. For more information, see Using an + * higher. For more information, see Using an * auto-termination policy.
*Creates or updates an auto-termination policy for an Amazon EMR cluster. An diff --git a/clients/client-emr/src/commands/RunJobFlowCommand.ts b/clients/client-emr/src/commands/RunJobFlowCommand.ts index e9a841d00ec4..8c112225595a 100644 --- a/clients/client-emr/src/commands/RunJobFlowCommand.ts +++ b/clients/client-emr/src/commands/RunJobFlowCommand.ts @@ -56,7 +56,7 @@ export interface RunJobFlowCommandOutput extends RunJobFlowOutput, __MetadataBea *
For long-running clusters, we recommend that you periodically store your results.
*The instance fleets configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions. The RunJobFlow request can contain + * 4.8.0 and higher, excluding 5.0.x versions. The RunJobFlow request can contain * InstanceFleets parameters or InstanceGroups parameters, but not both.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is - * available in Amazon EMR releases 5.12.1 and later.
+ * 4.8.0 and higher, excluding 5.0.x versions. On-Demand Instances allocation strategy is + * available in Amazon EMR releases 5.12.1 and higher. *The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions. Spot Instance allocation strategy is - * available in Amazon EMR releases 5.12.1 and later.
+ * 4.8.0 and higher, excluding 5.0.x versions. Spot Instance allocation strategy is + * available in Amazon EMR releases 5.12.1 and higher. *Spot Instances with a defined duration (also known as Spot blocks) are no longer @@ -317,9 +317,17 @@ export interface SpotProvisioningSpecification { /** * @public - *
Specifies the strategy to use in launching Spot Instance fleets. Currently, the only - * option is capacity-optimized (the default), which launches instances from Spot Instance - * pools with optimal capacity for the number of instances that are launching.
+ *Specifies one of the following strategies to launch Spot Instance fleets:
+ * price-capacity-optimized, capacity-optimized,
+ * lowest-price, or diversified. For more information on the
+ * provisioning strategies, see Allocation strategies
+ * for Spot Instances in the Amazon EC2 User Guide for Linux
+ * Instances.
When you launch a Spot Instance fleet with the old console, it automatically launches
+ * with the capacity-optimized strategy. You can't change the allocation
+ * strategy from the old console.
The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions. On-Demand and Spot instance allocation - * strategies are available in Amazon EMR releases 5.12.1 and later.
+ * 4.8.0 and higher, excluding 5.0.x versions. On-Demand and Spot instance allocation + * strategies are available in Amazon EMR releases 5.12.1 and higher. *The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is - * available in Amazon EMR releases 5.12.1 and later.
+ * 4.8.0 and higher, excluding 5.0.x versions. On-Demand Instances allocation strategy is + * available in Amazon EMR releases 5.12.1 and higher. *With Amazon EMR release version 4.0 and later, the only accepted parameter is + *
With Amazon EMR release version 4.0 and higher, the only accepted parameter is * the application name. To pass arguments to applications, you use configuration * classifications specified using configuration JSON objects. For more information, see * Configuring Applications.
@@ -1429,7 +1437,7 @@ export type CancelStepsRequestStatus = (typeof CancelStepsRequestStatus)[keyof t /** * @public - *Specification of the status of a CancelSteps request. Available only in Amazon EMR version 4.8.0 and later, excluding version 5.0.0.
+ *Specification of the status of a CancelSteps request. Available only in Amazon EMR version 4.8.0 and higher, excluding version 5.0.0.
*/ export interface CancelStepsInfo { /** @@ -2549,7 +2557,7 @@ export interface PlacementType { * instance groups. *The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *The KMS key used for encrypting log files. This attribute is only - * available with Amazon EMR 5.30.0 and later, excluding 6.0.0.
+ * available with Amazon EMR 5.30.0 and higher, excluding 6.0.0. */ LogEncryptionKmsKeyId?: string; /** * @public *Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR
- * releases 4.0 and later, ReleaseLabel is used. To specify a custom AMI, use
+ * releases 4.0 and higher, ReleaseLabel is used. To specify a custom AMI, use
* CustomAmiID.
TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates
* nodes at the instance-hour boundary, regardless of when the request to terminate the
* instance was submitted. This option is only available with Amazon EMR 5.1.0 and
- * later and is the default for clusters created using that version.
+ * higher and is the default for clusters created using that version.
* TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes
* to a deny list and drains tasks from nodes before terminating the Amazon EC2
* instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to
- * HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and later, and is the default for releases of Amazon EMR earlier than 5.1.0.
+ * HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and higher, and is the default for releases of Amazon EMR earlier than 5.1.0.
*/
ScaleDownBehavior?: ScaleDownBehavior;
}
@@ -4084,7 +4092,7 @@ export type InstanceFleetStateChangeReasonCode =
* Provides status change reason details for the instance fleet.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *The status of the instance fleet.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *The amount of memory that is available to Amazon EMR from the SupportedInstanceType. The kernel and hypervisor
- * software consume some memory, so this value might be lower than the overall memory for the
- * instance type.
The amount of memory that is available to Amazon EMR from the
+ * SupportedInstanceType. The kernel and hypervisor software consume some
+ * memory, so this value might be lower than the overall memory for the instance type.
Configuration parameters for an instance fleet modification request.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *Amazon EMR releases 4.x or later.
+ *Amazon EMR releases 4.x or higher.
*An optional configuration specification to be used when provisioning cluster instances,
* which can include configurations for applications and software bundled with Amazon EMR. A configuration consists of a classification, properties, and optional
@@ -6051,7 +6059,7 @@ export interface Cluster {
* @public
* The instance fleet configuration is available only in Amazon EMR releases
- * 4.8.0 and later, excluding 5.0.x versions.
The instance group configuration of the cluster. A value of INSTANCE_GROUP
* indicates a uniform instance group configuration. A value of INSTANCE_FLEET
@@ -6069,7 +6077,7 @@ export interface Cluster {
/**
* @public
*
The KMS key used for encrypting log files. This attribute is only - * available with Amazon EMR 5.30.0 and later, excluding Amazon EMR 6.0.0. + * available with Amazon EMR 5.30.0 and higher, excluding Amazon EMR 6.0.0. *
*/ LogEncryptionKmsKeyId?: string; @@ -6093,7 +6101,7 @@ export interface Cluster { *emr-x.x.x, where x.x.x is an Amazon EMR release version such as
* emr-5.14.0. For more information about Amazon EMR release versions
* and included application versions and features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release label applies only to Amazon EMR
- * releases version 4.0 and later. Earlier versions use AmiVersion.
+ * releases version 4.0 and higher. Earlier versions use AmiVersion.
*/
ReleaseLabel?: string;
@@ -6161,7 +6169,7 @@ export interface Cluster {
/**
* @public
- * Applies only to Amazon EMR releases 4.x and later. The list of configurations + *
Applies only to Amazon EMR releases 4.x and higher. The list of configurations * that are supplied to the Amazon EMR cluster.
*/ Configurations?: Configuration[]; @@ -6187,26 +6195,26 @@ export interface Cluster { *TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates
* nodes at the instance-hour boundary, regardless of when the request to terminate the
* instance was submitted. This option is only available with Amazon EMR 5.1.0 and
- * later and is the default for clusters created using that version.
+ * higher and is the default for clusters created using that version.
* TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes
* to a deny list and drains tasks from nodes before terminating the Amazon EC2
* instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to
- * HDFS corruption. TERMINATE_AT_TASK_COMPLETION is available only in Amazon EMR releases 4.1.0 and later, and is the default for versions of Amazon EMR earlier than 5.1.0.
+ * HDFS corruption. TERMINATE_AT_TASK_COMPLETION is available only in Amazon EMR releases 4.1.0 and higher, and is the default for versions of Amazon EMR earlier than 5.1.0.
*/
ScaleDownBehavior?: ScaleDownBehavior;
/**
* @public
- * Available only in Amazon EMR releases 5.7.0 and later. The ID of a custom Amazon - * EBS-backed Linux AMI if the cluster uses a custom AMI.
+ *Available only in Amazon EMR releases 5.7.0 and higher. The ID of a custom + * Amazon EBS-backed Linux AMI if the cluster uses a custom AMI.
*/ CustomAmiId?: string; /** * @public - *The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is - * used for each Amazon EC2 instance. Available in Amazon EMR releases 4.x and - * later.
+ *The size, in GiB, of the Amazon EBS root device volume for the Linux AMI that + * each Amazon EC2 instance uses. Available in Amazon EMR releases 4.x and + * higher.
*/ EbsRootVolumeSize?: number; @@ -6257,6 +6265,22 @@ export interface Cluster { * response. */ OSReleaseLabel?: string; + + /** + * @public + *The IOPS, of the Amazon EBS root device volume for the Linux AMI that each + * Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0 and + * higher.
+ */ + EbsRootVolumeIops?: number; + + /** + * @public + *The throughput, in MiB/s, of the Amazon EBS root device volume for the Linux AMI + * that each Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0 + * and higher.
+ */ + EbsRootVolumeThroughput?: number; } /** @@ -6305,7 +6329,7 @@ export interface InstanceGroupConfig { /** * @public *Amazon EMR releases 4.x or later.
+ *Amazon EMR releases 4.x or higher.
*The list of configurations supplied for an Amazon EMR cluster instance group. * You can specify a separate configuration for each instance group (master, core, and @@ -6390,7 +6414,7 @@ export interface InstanceGroupModifyConfig { * instance type configurations for a fleet.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *The configuration specification for each instance type in an instance fleet.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *PermittedPublicSecurityGroupRuleRanges in the
* BlockPublicAccessConfiguration. By default, Port 22 (SSH) is an exception,
- * and public access is allowed on this port. You can change this by updating the block public
- * access configuration to remove the exception.
+ * and public access is allowed on this port. To change this, update the block public access
+ * configuration to remove the exception.
* For accounts that created clusters in a Region before November 25, 2019, block public * access is disabled by default in that Region. To use this feature, you must manually @@ -6616,7 +6640,7 @@ export interface AddInstanceGroupsInput { * provisioned to meet a defined target capacity.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *The configuration that defines an instance fleet.
*The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *Amazon EMR releases 4.x or later.
+ *Amazon EMR releases 4.x or higher.
*The list of configurations supplied for an Amazon EMR cluster instance group.
* You can specify a separate configuration for each instance group (master, core, and
@@ -7050,7 +7074,7 @@ export interface JobFlowInstancesConfig {
* @public
* The instance fleet configuration is available only in Amazon EMR releases
- * 4.8.0 and later, excluding 5.0.x versions.
Describes the Amazon EC2 instances and instance configurations for clusters that * use the instance fleet configuration.
@@ -7114,7 +7138,7 @@ export interface JobFlowInstancesConfig { * instances in the optimal subnet. *The instance fleet configuration is available only in Amazon EMR releases - * 4.8.0 and later, excluding 5.0.x versions.
+ * 4.8.0 and higher, excluding 5.0.x versions. *Input to the RunJobFlow operation.
+ *Input to the RunJobFlow operation.
*/ export interface RunJobFlowInput { /** @@ -7178,7 +7202,8 @@ export interface RunJobFlowInput { * @public *The KMS key used for encrypting log files. If a value is not * provided, the logs remain encrypted by AES-256. This attribute is only available with - * Amazon EMR releases 5.30.0 and later, excluding Amazon EMR 6.0.0.
+ * Amazon EMR releases 5.30.0 and higher, excluding Amazon EMR + * 6.0.0. */ LogEncryptionKmsKeyId?: string; @@ -7191,7 +7216,7 @@ export interface RunJobFlowInput { /** * @public *Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR
- * releases 4.0 and later, ReleaseLabel is used. To specify a custom AMI, use
+ * releases 4.0 and higher, ReleaseLabel is used. To specify a custom AMI, use
* CustomAmiID.
emr-x.x.x, where x.x.x is an Amazon EMR release version such as
* emr-5.14.0. For more information about Amazon EMR release versions
* and included application versions and features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release label applies only to Amazon EMR
- * releases version 4.0 and later. Earlier versions use AmiVersion.
+ * releases version 4.0 and higher. Earlier versions use AmiVersion.
*/
ReleaseLabel?: string;
@@ -7229,7 +7254,7 @@ export interface RunJobFlowInput {
* @public
* For Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and - * later, use Applications.
+ * higher, use Applications. *A list of strings that indicates third-party software to use. For more information, see * the Amazon EMR Developer Guide. Currently supported values are:
@@ -7248,7 +7273,7 @@ export interface RunJobFlowInput { * @public *For Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and - * later, use Applications.
+ * higher, use Applications. *A list of strings that indicates third-party software to use with the job flow that * accepts a user argument list. Amazon EMR accepts and forwards the argument list to @@ -7288,7 +7313,7 @@ export interface RunJobFlowInput { /** * @public - *
Applies to Amazon EMR releases 4.0 and later. A case-insensitive list of + *
Applies to Amazon EMR releases 4.0 and higher. A case-insensitive list of
* applications for Amazon EMR to install and configure when launching the cluster.
* For a list of applications available for each Amazon EMR release version, see the
* Amazon EMRRelease
@@ -7298,7 +7323,7 @@ export interface RunJobFlowInput {
/**
* @public
- * For Amazon EMR releases 4.0 and later. The list of configurations supplied for
+ * For Amazon EMR releases 4.0 and higher. The list of configurations supplied for
* the Amazon EMR cluster that you are creating.TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates
* nodes at the instance-hour boundary, regardless of when the request to terminate the
* instance was submitted. This option is only available with Amazon EMR 5.1.0 and
- * later and is the default for clusters created using that version.
+ * higher and is the default for clusters created using that version.
* TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes
* to a deny list and drains tasks from nodes before terminating the Amazon EC2
* instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to
- * HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and later, and is the default for releases of Amazon EMR earlier than 5.1.0.
TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and higher, and is the default for releases of Amazon EMR earlier than 5.1.0.
*/
ScaleDownBehavior?: ScaleDownBehavior;
/**
* @public
- * Available only in Amazon EMR releases 5.7.0 and later. The ID of a custom Amazon - * EBS-backed Linux AMI. If specified, Amazon EMR uses this AMI when it launches - * cluster Amazon EC2 instances. For more information about custom AMIs in Amazon EMR, see Using a Custom AMI in the + *
Available only in Amazon EMR releases 5.7.0 and higher. The ID of a custom
+ * Amazon EBS-backed Linux AMI. If specified, Amazon EMR uses this AMI when it
+ * launches cluster Amazon EC2 instances. For more information about custom AMIs in
+ * Amazon EMR, see Using a Custom AMI in the
* Amazon EMR Management Guide. If omitted, the cluster
* uses the base Linux AMI for the ReleaseLabel specified. For Amazon EMR
* releases 2.x and 3.x, use AmiVersion instead.
The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is - * used for each Amazon EC2 instance. Available in Amazon EMR releases 4.x and - * later.
+ *The size, in GiB, of the Amazon EBS root device volume for the Linux AMI that + * each Amazon EC2 instance uses. Available in Amazon EMR releases 4.x and + * higher.
*/ EbsRootVolumeSize?: number; @@ -7448,6 +7474,22 @@ export interface RunJobFlowInput { * Linux release for cluster launch. */ OSReleaseLabel?: string; + + /** + * @public + *The IOPS for the Amazon EBS root device volume for the Linux AMI that each + * Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0 and + * higher.
+ */ + EbsRootVolumeIops?: number; + + /** + * @public + *The throughput, in MiB/s, of the Amazon EBS root device volume for the Linux AMI + * that each Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0 + * and higher.
+ */ + EbsRootVolumeThroughput?: number; } /** diff --git a/clients/client-emr/src/protocols/Aws_json1_1.ts b/clients/client-emr/src/protocols/Aws_json1_1.ts index 11681f1eedcb..6e12c48c2055 100644 --- a/clients/client-emr/src/protocols/Aws_json1_1.ts +++ b/clients/client-emr/src/protocols/Aws_json1_1.ts @@ -4057,7 +4057,9 @@ const se_RunJobFlowInput = (input: RunJobFlowInput, context: __SerdeContext): an BootstrapActions: _json, Configurations: (_) => se_ConfigurationList(_, context), CustomAmiId: [], + EbsRootVolumeIops: [], EbsRootVolumeSize: [], + EbsRootVolumeThroughput: [], Instances: (_) => se_JobFlowInstancesConfig(_, context), JobFlowRole: [], KerberosAttributes: _json, @@ -4266,7 +4268,9 @@ const de_Cluster = (output: any, context: __SerdeContext): Cluster => { ClusterArn: __expectString, Configurations: (_: any) => de_ConfigurationList(_, context), CustomAmiId: __expectString, + EbsRootVolumeIops: __expectInt32, EbsRootVolumeSize: __expectInt32, + EbsRootVolumeThroughput: __expectInt32, Ec2InstanceAttributes: _json, Id: __expectString, InstanceCollectionType: __expectString, diff --git a/codegen/sdk-codegen/aws-models/emr.json b/codegen/sdk-codegen/aws-models/emr.json index 50728d2fbff3..2df72b3c8c11 100644 --- a/codegen/sdk-codegen/aws-models/emr.json +++ b/codegen/sdk-codegen/aws-models/emr.json @@ -75,7 +75,7 @@ } ], "traits": { - "smithy.api#documentation": "Adds an instance fleet to a running cluster.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x.
\nAdds an instance fleet to a running cluster.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x.
\nWith Amazon EMR release version 4.0 and later, the only accepted parameter is\n the application name. To pass arguments to applications, you use configuration\n classifications specified using configuration JSON objects. For more information, see\n Configuring Applications.
\nWith earlier Amazon EMR releases, the application is any Amazon or third-party\n software that you can add to the cluster. This structure contains a list of strings that\n indicates the software to use with the cluster and accepts a user argument list. Amazon EMR accepts and forwards the argument list to the corresponding installation\n script as bootstrap action argument.
" + "smithy.api#documentation": "With Amazon EMR release version 4.0 and higher, the only accepted parameter is\n the application name. To pass arguments to applications, you use configuration\n classifications specified using configuration JSON objects. For more information, see\n Configuring Applications.
\nWith earlier Amazon EMR releases, the application is any Amazon or third-party\n software that you can add to the cluster. This structure contains a list of strings that\n indicates the software to use with the cluster and accepts a user argument list. Amazon EMR accepts and forwards the argument list to the corresponding installation\n script as bootstrap action argument.
" } }, "com.amazonaws.emr#ApplicationList": { @@ -705,7 +705,7 @@ } ], "traits": { - "smithy.api#documentation": "Cancels a pending step or steps in a running cluster. Available only in Amazon EMR versions 4.8.0 and later, excluding version 5.0.0. A maximum of 256 steps are allowed in\n each CancelSteps request. CancelSteps is idempotent but asynchronous; it does not guarantee\n that a step will be canceled, even if the request is successfully submitted. When you use\n Amazon EMR releases 5.28.0 and later, you can cancel steps that are in a\n PENDING or RUNNING state. In earlier versions of Amazon EMR, you can only cancel steps that are in a PENDING state.
Cancels a pending step or steps in a running cluster. Available only in Amazon EMR versions 4.8.0 and higher, excluding version 5.0.0. A maximum of 256 steps are allowed\n in each CancelSteps request. CancelSteps is idempotent but asynchronous; it does not\n guarantee that a step will be canceled, even if the request is successfully submitted. When\n you use Amazon EMR releases 5.28.0 and higher, you can cancel steps that are in a\n PENDING or RUNNING state. In earlier versions of Amazon EMR, you can only cancel steps that are in a PENDING state.
Specification of the status of a CancelSteps request. Available only in Amazon EMR version 4.8.0 and later, excluding version 5.0.0.
" + "smithy.api#documentation": "Specification of the status of a CancelSteps request. Available only in Amazon EMR version 4.8.0 and higher, excluding version 5.0.0.
" } }, "com.amazonaws.emr#CancelStepsInfoList": { @@ -903,7 +903,7 @@ "InstanceCollectionType": { "target": "com.amazonaws.emr#InstanceCollectionType", "traits": { - "smithy.api#documentation": "The instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nThe instance group configuration of the cluster. A value of INSTANCE_GROUP\n indicates a uniform instance group configuration. A value of INSTANCE_FLEET\n indicates an instance fleets configuration.
The instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe instance group configuration of the cluster. A value of INSTANCE_GROUP\n indicates a uniform instance group configuration. A value of INSTANCE_FLEET\n indicates an instance fleets configuration.
The KMS key used for encrypting log files. This attribute is only\n available with Amazon EMR 5.30.0 and later, excluding Amazon EMR 6.0.0.\n
" + "smithy.api#documentation": "The KMS key used for encrypting log files. This attribute is only\n available with Amazon EMR 5.30.0 and higher, excluding Amazon EMR 6.0.0.\n
" } }, "RequestedAmiVersion": { @@ -933,7 +933,7 @@ "ReleaseLabel": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The Amazon EMR release label, which determines the version of open-source\n application packages installed on the cluster. Release labels are in the form\n emr-x.x.x, where x.x.x is an Amazon EMR release version such as\n emr-5.14.0. For more information about Amazon EMR release versions\n and included application versions and features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release label applies only to Amazon EMR\n releases version 4.0 and later. Earlier versions use AmiVersion.
The Amazon EMR release label, which determines the version of open-source\n application packages installed on the cluster. Release labels are in the form\n emr-x.x.x, where x.x.x is an Amazon EMR release version such as\n emr-5.14.0. For more information about Amazon EMR release versions\n and included application versions and features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release label applies only to Amazon EMR\n releases version 4.0 and higher. Earlier versions use AmiVersion.
Applies only to Amazon EMR releases 4.x and later. The list of configurations\n that are supplied to the Amazon EMR cluster.
" + "smithy.api#documentation": "Applies only to Amazon EMR releases 4.x and higher. The list of configurations\n that are supplied to the Amazon EMR cluster.
" } }, "SecurityConfiguration": { @@ -1005,19 +1005,19 @@ "ScaleDownBehavior": { "target": "com.amazonaws.emr#ScaleDownBehavior", "traits": { - "smithy.api#documentation": "The way that individual Amazon EC2 instances terminate when an automatic\n scale-in activity occurs or an instance group is resized.\n TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates\n nodes at the instance-hour boundary, regardless of when the request to terminate the\n instance was submitted. This option is only available with Amazon EMR 5.1.0 and\n later and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes\n to a deny list and drains tasks from nodes before terminating the Amazon EC2\n instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to\n HDFS corruption. TERMINATE_AT_TASK_COMPLETION is available only in Amazon EMR releases 4.1.0 and later, and is the default for versions of Amazon EMR earlier than 5.1.0.
The way that individual Amazon EC2 instances terminate when an automatic\n scale-in activity occurs or an instance group is resized.\n TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates\n nodes at the instance-hour boundary, regardless of when the request to terminate the\n instance was submitted. This option is only available with Amazon EMR 5.1.0 and\n higher and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes\n to a deny list and drains tasks from nodes before terminating the Amazon EC2\n instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to\n HDFS corruption. TERMINATE_AT_TASK_COMPLETION is available only in Amazon EMR releases 4.1.0 and higher, and is the default for versions of Amazon EMR earlier than 5.1.0.
Available only in Amazon EMR releases 5.7.0 and later. The ID of a custom Amazon\n EBS-backed Linux AMI if the cluster uses a custom AMI.
" + "smithy.api#documentation": "Available only in Amazon EMR releases 5.7.0 and higher. The ID of a custom\n Amazon EBS-backed Linux AMI if the cluster uses a custom AMI.
" } }, "EbsRootVolumeSize": { "target": "com.amazonaws.emr#Integer", "traits": { - "smithy.api#documentation": "The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is\n used for each Amazon EC2 instance. Available in Amazon EMR releases 4.x and\n later.
" + "smithy.api#documentation": "The size, in GiB, of the Amazon EBS root device volume for the Linux AMI that\n each Amazon EC2 instance uses. Available in Amazon EMR releases 4.x and\n higher.
" } }, "RepoUpgradeOnBoot": { @@ -1061,6 +1061,18 @@ "traits": { "smithy.api#documentation": "The Amazon Linux release specified in a cluster launch RunJobFlow request. If no Amazon\n Linux release was specified, the default Amazon Linux release is shown in the\n response.
" } + }, + "EbsRootVolumeIops": { + "target": "com.amazonaws.emr#Integer", + "traits": { + "smithy.api#documentation": "The IOPS, of the Amazon EBS root device volume for the Linux AMI that each\n Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0 and\n higher.
" + } + }, + "EbsRootVolumeThroughput": { + "target": "com.amazonaws.emr#Integer", + "traits": { + "smithy.api#documentation": "The throughput, in MiB/s, of the Amazon EBS root device volume for the Linux AMI\n that each Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0\n and higher.
" + } } }, "traits": { @@ -1455,7 +1467,7 @@ } }, "traits": { - "smithy.api#documentation": "Amazon EMR releases 4.x or later.
\nAn optional configuration specification to be used when provisioning cluster instances,\n which can include configurations for applications and software bundled with Amazon EMR. A configuration consists of a classification, properties, and optional\n nested configurations. A classification refers to an application-specific configuration\n file. Properties are the settings you want to change in that file. For more information,\n see Configuring Applications.
" + "smithy.api#documentation": "Amazon EMR releases 4.x or higher.
\nAn optional configuration specification to be used when provisioning cluster instances,\n which can include configurations for applications and software bundled with Amazon EMR. A configuration consists of a classification, properties, and optional\n nested configurations. A classification refers to an application-specific configuration\n file. Properties are the settings you want to change in that file. For more information,\n see Configuring Applications.
" } }, "com.amazonaws.emr#ConfigurationList": { @@ -4039,7 +4051,7 @@ "target": "com.amazonaws.emr#BlockPublicAccessConfiguration", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "A configuration for Amazon EMR block public access. The configuration applies to\n all clusters created in your account for the current Region. The configuration specifies\n whether block public access is enabled. If block public access is enabled, security groups\n associated with the cluster cannot have rules that allow inbound traffic from 0.0.0.0/0 or\n ::/0 on a port, unless the port is specified as an exception using\n PermittedPublicSecurityGroupRuleRanges in the\n BlockPublicAccessConfiguration. By default, Port 22 (SSH) is an exception,\n and public access is allowed on this port. You can change this by updating the block public\n access configuration to remove the exception.
For accounts that created clusters in a Region before November 25, 2019, block public\n access is disabled by default in that Region. To use this feature, you must manually\n enable and configure it. For accounts that did not create an Amazon EMR cluster\n in a Region before this date, block public access is enabled by default in that\n Region.
\nA configuration for Amazon EMR block public access. The configuration applies to\n all clusters created in your account for the current Region. The configuration specifies\n whether block public access is enabled. If block public access is enabled, security groups\n associated with the cluster cannot have rules that allow inbound traffic from 0.0.0.0/0 or\n ::/0 on a port, unless the port is specified as an exception using\n PermittedPublicSecurityGroupRuleRanges in the\n BlockPublicAccessConfiguration. By default, Port 22 (SSH) is an exception,\n and public access is allowed on this port. To change this, update the block public access\n configuration to remove the exception.
For accounts that created clusters in a Region before November 25, 2019, block public\n access is disabled by default in that Region. To use this feature, you must manually\n enable and configure it. For accounts that did not create an Amazon EMR cluster\n in a Region before this date, block public access is enabled by default in that\n Region.
\nDescribes an instance fleet, which is a group of Amazon EC2 instances that host\n a particular node type (master, core, or task) in an Amazon EMR cluster. Instance\n fleets can consist of a mix of instance types and On-Demand and Spot Instances, which are\n provisioned to meet a defined target capacity.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nDescribes an instance fleet, which is a group of Amazon EC2 instances that host\n a particular node type (master, core, or task) in an Amazon EMR cluster. Instance\n fleets can consist of a mix of instance types and On-Demand and Spot Instances, which are\n provisioned to meet a defined target capacity.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe configuration that defines an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nThe configuration that defines an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nConfiguration parameters for an instance fleet modification request.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nConfiguration parameters for an instance fleet modification request.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe launch specification for On-Demand Instances in the instance fleet, which\n determines the allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is\n available in Amazon EMR releases 5.12.1 and later.
\nThe launch specification for On-Demand Instances in the instance fleet, which\n determines the allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions. On-Demand Instances allocation strategy is\n available in Amazon EMR releases 5.12.1 and higher.
\nThe launch specification for Spot Instances in the fleet, which determines the defined\n duration, provisioning timeout behavior, and allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions. On-Demand and Spot instance allocation\n strategies are available in Amazon EMR releases 5.12.1 and later.
\nThe launch specification for Spot Instances in the fleet, which determines the defined\n duration, provisioning timeout behavior, and allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions. On-Demand and Spot instance allocation\n strategies are available in Amazon EMR releases 5.12.1 and higher.
\nProvides status change reason details for the instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nProvides status change reason details for the instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe status of the instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nThe status of the instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nProvides historical timestamps for the instance fleet, including the time of creation,\n the time it became ready to run jobs, and the time of termination.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nProvides historical timestamps for the instance fleet, including the time of creation,\n the time it became ready to run jobs, and the time of termination.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nAmazon EMR releases 4.x or later.
\nThe list of configurations supplied for an Amazon EMR cluster instance group.\n You can specify a separate configuration for each instance group (master, core, and\n task).
" + "smithy.api#documentation": "Amazon EMR releases 4.x or higher.
\nThe list of configurations supplied for an Amazon EMR cluster instance group.\n You can specify a separate configuration for each instance group (master, core, and\n task).
" } }, "ConfigurationsVersion": { @@ -4972,7 +4984,7 @@ "Configurations": { "target": "com.amazonaws.emr#ConfigurationList", "traits": { - "smithy.api#documentation": "Amazon EMR releases 4.x or later.
\nThe list of configurations supplied for an Amazon EMR cluster instance group.\n You can specify a separate configuration for each instance group (master, core, and\n task).
" + "smithy.api#documentation": "Amazon EMR releases 4.x or higher.
\nThe list of configurations supplied for an Amazon EMR cluster instance group.\n You can specify a separate configuration for each instance group (master, core, and\n task).
" } }, "EbsConfiguration": { @@ -5655,7 +5667,7 @@ } }, "traits": { - "smithy.api#documentation": "An instance type configuration for each instance type in an instance fleet, which\n determines the Amazon EC2 instances Amazon EMR attempts to provision to\n fulfill On-Demand and Spot target capacities. When you use an allocation strategy, you can\n include a maximum of 30 instance type configurations for a fleet. For more information\n about how to use an allocation strategy, see Configure Instance\n Fleets. Without an allocation strategy, you may specify a maximum of five\n instance type configurations for a fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nAn instance type configuration for each instance type in an instance fleet, which\n determines the Amazon EC2 instances Amazon EMR attempts to provision to\n fulfill On-Demand and Spot target capacities. When you use an allocation strategy, you can\n include a maximum of 30 instance type configurations for a fleet. For more information\n about how to use an allocation strategy, see Configure Instance\n Fleets. Without an allocation strategy, you may specify a maximum of five\n instance type configurations for a fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe configuration specification for each instance type in an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nThe configuration specification for each instance type in an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe KMS key used for encrypting log files. This attribute is only\n available with Amazon EMR 5.30.0 and later, excluding 6.0.0.
" + "smithy.api#documentation": "The KMS key used for encrypting log files. This attribute is only\n available with Amazon EMR 5.30.0 and higher, excluding 6.0.0.
" } }, "AmiVersion": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR\n releases 4.0 and later, ReleaseLabel is used. To specify a custom AMI, use\n CustomAmiID.
Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR\n releases 4.0 and higher, ReleaseLabel is used. To specify a custom AMI, use\n CustomAmiID.
The way that individual Amazon EC2 instances terminate when an automatic\n scale-in activity occurs or an instance group is resized.\n TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates\n nodes at the instance-hour boundary, regardless of when the request to terminate the\n instance was submitted. This option is only available with Amazon EMR 5.1.0 and\n later and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes\n to a deny list and drains tasks from nodes before terminating the Amazon EC2\n instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to\n HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and later, and is the default for releases of Amazon EMR earlier than 5.1.0.
The way that individual Amazon EC2 instances terminate when an automatic\n scale-in activity occurs or an instance group is resized.\n TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates\n nodes at the instance-hour boundary, regardless of when the request to terminate the\n instance was submitted. This option is only available with Amazon EMR 5.1.0 and\n higher and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes\n to a deny list and drains tasks from nodes before terminating the Amazon EC2\n instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to\n HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and higher, and is the default for releases of Amazon EMR earlier than 5.1.0.
The instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nDescribes the Amazon EC2 instances and instance configurations for clusters that\n use the instance fleet configuration.
" + "smithy.api#documentation": "The instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nDescribes the Amazon EC2 instances and instance configurations for clusters that\n use the instance fleet configuration.
" } }, "Ec2KeyName": { @@ -6072,7 +6084,7 @@ "Ec2SubnetIds": { "target": "com.amazonaws.emr#XmlStringMaxLen256List", "traits": { - "smithy.api#documentation": "Applies to clusters that use the instance fleet configuration. When multiple Amazon EC2 subnet IDs are specified, Amazon EMR evaluates them and launches\n instances in the optimal subnet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nApplies to clusters that use the instance fleet configuration. When multiple Amazon EC2 subnet IDs are specified, Amazon EMR evaluates them and launches\n instances in the optimal subnet.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nLists all available details about the instance fleets in a cluster.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nLists all available details about the instance fleets in a cluster.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nA list of the instance types that Amazon EMR supports. You can filter the\n list by Amazon Web Services Region and Amazon EMR release.
", + "smithy.api#documentation": "A list of the instance types that Amazon EMR supports. You can filter the list\n by Amazon Web Services Region and Amazon EMR release.
", "smithy.api#paginated": { "inputToken": "Marker", "outputToken": "Marker" @@ -7294,7 +7306,7 @@ } ], "traits": { - "smithy.api#documentation": "Modifies the target On-Demand and target Spot capacities for the instance fleet with the\n specified InstanceFleetID within the cluster specified using ClusterID. The call either\n succeeds or fails atomically.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nModifies the target On-Demand and target Spot capacities for the instance fleet with the\n specified InstanceFleetID within the cluster specified using ClusterID. The call either\n succeeds or fails atomically.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nThe launch specification for On-Demand Instances in the instance fleet, which\n determines the allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is\n available in Amazon EMR releases 5.12.1 and later.
\nThe launch specification for On-Demand Instances in the instance fleet, which\n determines the allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions. On-Demand Instances allocation strategy is\n available in Amazon EMR releases 5.12.1 and higher.
\nWhen multiple Availability Zones are specified, Amazon EMR evaluates them and\n launches instances in the optimal Availability Zone. AvailabilityZones is used\n for instance fleets, while AvailabilityZone (singular) is used for uniform\n instance groups.
The instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions.
\nWhen multiple Availability Zones are specified, Amazon EMR evaluates them and\n launches instances in the optimal Availability Zone. AvailabilityZones is used\n for instance fleets, while AvailabilityZone (singular) is used for uniform\n instance groups.
The instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions.
\nAuto-termination is supported in Amazon EMR releases 5.30.0 and 6.1.0 and\n later. For more information, see Using an\n auto-termination policy.
\nCreates or updates an auto-termination policy for an Amazon EMR cluster. An\n auto-termination policy defines the amount of idle time in seconds after which a cluster\n automatically terminates. For alternative cluster termination options, see Control\n cluster termination.
" + "smithy.api#documentation": "Auto-termination is supported in Amazon EMR releases 5.30.0 and 6.1.0 and\n higher. For more information, see Using an\n auto-termination policy.
\nCreates or updates an auto-termination policy for an Amazon EMR cluster. An\n auto-termination policy defines the amount of idle time in seconds after which a cluster\n automatically terminates. For alternative cluster termination options, see Control\n cluster termination.
" } }, "com.amazonaws.emr#PutAutoTerminationPolicyInput": { @@ -8387,7 +8399,7 @@ } ], "traits": { - "smithy.api#documentation": "RunJobFlow creates and starts running a new cluster (job flow). The cluster runs the\n steps specified. After the steps complete, the cluster stops and the HDFS partition is\n lost. To prevent loss of data, configure the last step of the job flow to store results in\n Amazon S3. If the JobFlowInstancesConfig\n KeepJobFlowAliveWhenNoSteps parameter is set to TRUE, the cluster\n transitions to the WAITING state rather than shutting down after the steps have completed.
For additional protection, you can set the JobFlowInstancesConfig\n TerminationProtected parameter to TRUE to lock the cluster and\n prevent it from being terminated by API call, user intervention, or in the event of a job\n flow error.
A maximum of 256 steps are allowed in each job flow.
\nIf your cluster is long-running (such as a Hive data warehouse) or complex, you may\n require more than 256 steps to process your data. You can bypass the 256-step limitation in\n various ways, including using the SSH shell to connect to the master node and submitting\n queries directly to the software running on the master node, such as Hive and\n Hadoop.
\nFor long-running clusters, we recommend that you periodically store your results.
\nThe instance fleets configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions. The RunJobFlow request can contain\n InstanceFleets parameters or InstanceGroups parameters, but not both.
\nRunJobFlow creates and starts running a new cluster (job flow). The cluster runs the\n steps specified. After the steps complete, the cluster stops and the HDFS partition is\n lost. To prevent loss of data, configure the last step of the job flow to store results in\n Amazon S3. If the JobFlowInstancesConfig\n KeepJobFlowAliveWhenNoSteps parameter is set to TRUE, the cluster\n transitions to the WAITING state rather than shutting down after the steps have completed.
For additional protection, you can set the JobFlowInstancesConfig\n TerminationProtected parameter to TRUE to lock the cluster and\n prevent it from being terminated by API call, user intervention, or in the event of a job\n flow error.
A maximum of 256 steps are allowed in each job flow.
\nIf your cluster is long-running (such as a Hive data warehouse) or complex, you may\n require more than 256 steps to process your data. You can bypass the 256-step limitation in\n various ways, including using the SSH shell to connect to the master node and submitting\n queries directly to the software running on the master node, such as Hive and\n Hadoop.
\nFor long-running clusters, we recommend that you periodically store your results.
\nThe instance fleets configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions. The RunJobFlow request can contain\n InstanceFleets parameters or InstanceGroups parameters, but not both.
\nThe KMS key used for encrypting log files. If a value is not\n provided, the logs remain encrypted by AES-256. This attribute is only available with\n Amazon EMR releases 5.30.0 and later, excluding Amazon EMR 6.0.0.
" + "smithy.api#documentation": "The KMS key used for encrypting log files. If a value is not\n provided, the logs remain encrypted by AES-256. This attribute is only available with\n Amazon EMR releases 5.30.0 and higher, excluding Amazon EMR\n 6.0.0.
" } }, "AdditionalInfo": { @@ -8422,13 +8434,13 @@ "AmiVersion": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR\n releases 4.0 and later, ReleaseLabel is used. To specify a custom AMI, use\n CustomAmiID.
Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR\n releases 4.0 and higher, ReleaseLabel is used. To specify a custom AMI, use\n CustomAmiID.
The Amazon EMR release label, which determines the version of open-source\n application packages installed on the cluster. Release labels are in the form\n emr-x.x.x, where x.x.x is an Amazon EMR release version such as\n emr-5.14.0. For more information about Amazon EMR release versions\n and included application versions and features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release label applies only to Amazon EMR\n releases version 4.0 and later. Earlier versions use AmiVersion.
The Amazon EMR release label, which determines the version of open-source\n application packages installed on the cluster. Release labels are in the form\n emr-x.x.x, where x.x.x is an Amazon EMR release version such as\n emr-5.14.0. For more information about Amazon EMR release versions\n and included application versions and features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release label applies only to Amazon EMR\n releases version 4.0 and higher. Earlier versions use AmiVersion.
For Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and\n later, use Applications.
\nA list of strings that indicates third-party software to use. For more information, see\n the Amazon EMR Developer Guide. Currently supported values are:
\n\"mapr-m3\" - launch the job flow using MapR M3 Edition.
\n\"mapr-m5\" - launch the job flow using MapR M5 Edition.
\nFor Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and\n higher, use Applications.
\nA list of strings that indicates third-party software to use. For more information, see\n the Amazon EMR Developer Guide. Currently supported values are:
\n\"mapr-m3\" - launch the job flow using MapR M3 Edition.
\n\"mapr-m5\" - launch the job flow using MapR M5 Edition.
\nFor Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and\n later, use Applications.
\nA list of strings that indicates third-party software to use with the job flow that\n accepts a user argument list. Amazon EMR accepts and forwards the argument list to\n the corresponding installation script as bootstrap action arguments. For more information,\n see \"Launch a Job Flow on the MapR Distribution for Hadoop\" in the Amazon EMR\n Developer Guide. Supported values are:
\n\"mapr-m3\" - launch the cluster using MapR M3 Edition.
\n\"mapr-m5\" - launch the cluster using MapR M5 Edition.
\n\"mapr\" with the user arguments specifying \"--edition,m3\" or \"--edition,m5\" -\n launch the job flow using MapR M3 or M5 Edition respectively.
\n\"mapr-m7\" - launch the cluster using MapR M7 Edition.
\n\"hunk\" - launch the cluster with the Hunk Big Data Analytics Platform.
\n\"hue\"- launch the cluster with Hue installed.
\n\"spark\" - launch the cluster with Apache Spark installed.
\n\"ganglia\" - launch the cluster with the Ganglia Monitoring System\n installed.
\nFor Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and\n higher, use Applications.
\nA list of strings that indicates third-party software to use with the job flow that\n accepts a user argument list. Amazon EMR accepts and forwards the argument list to\n the corresponding installation script as bootstrap action arguments. For more information,\n see \"Launch a Job Flow on the MapR Distribution for Hadoop\" in the Amazon EMR\n Developer Guide. Supported values are:
\n\"mapr-m3\" - launch the cluster using MapR M3 Edition.
\n\"mapr-m5\" - launch the cluster using MapR M5 Edition.
\n\"mapr\" with the user arguments specifying \"--edition,m3\" or \"--edition,m5\" -\n launch the job flow using MapR M3 or M5 Edition respectively.
\n\"mapr-m7\" - launch the cluster using MapR M7 Edition.
\n\"hunk\" - launch the cluster with the Hunk Big Data Analytics Platform.
\n\"hue\"- launch the cluster with Hue installed.
\n\"spark\" - launch the cluster with Apache Spark installed.
\n\"ganglia\" - launch the cluster with the Ganglia Monitoring System\n installed.
\nApplies to Amazon EMR releases 4.0 and later. A case-insensitive list of\n applications for Amazon EMR to install and configure when launching the cluster.\n For a list of applications available for each Amazon EMR release version, see the\n Amazon EMRRelease\n Guide.
" + "smithy.api#documentation": "Applies to Amazon EMR releases 4.0 and higher. A case-insensitive list of\n applications for Amazon EMR to install and configure when launching the cluster.\n For a list of applications available for each Amazon EMR release version, see the\n Amazon EMRRelease\n Guide.
" } }, "Configurations": { "target": "com.amazonaws.emr#ConfigurationList", "traits": { - "smithy.api#documentation": "For Amazon EMR releases 4.0 and later. The list of configurations supplied for\n the Amazon EMR cluster that you are creating.
" + "smithy.api#documentation": "For Amazon EMR releases 4.0 and higher. The list of configurations supplied for\n the Amazon EMR cluster that you are creating.
" } }, "VisibleToAllUsers": { @@ -8514,19 +8526,19 @@ "ScaleDownBehavior": { "target": "com.amazonaws.emr#ScaleDownBehavior", "traits": { - "smithy.api#documentation": "Specifies the way that individual Amazon EC2 instances terminate when an\n automatic scale-in activity occurs or an instance group is resized.\n TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates\n nodes at the instance-hour boundary, regardless of when the request to terminate the\n instance was submitted. This option is only available with Amazon EMR 5.1.0 and\n later and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes\n to a deny list and drains tasks from nodes before terminating the Amazon EC2\n instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to\n HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and later, and is the default for releases of Amazon EMR earlier than 5.1.0.
Specifies the way that individual Amazon EC2 instances terminate when an\n automatic scale-in activity occurs or an instance group is resized.\n TERMINATE_AT_INSTANCE_HOUR indicates that Amazon EMR terminates\n nodes at the instance-hour boundary, regardless of when the request to terminate the\n instance was submitted. This option is only available with Amazon EMR 5.1.0 and\n higher and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes\n to a deny list and drains tasks from nodes before terminating the Amazon EC2\n instances, regardless of the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes first and blocks instance termination if it could lead to\n HDFS corruption. TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR releases 4.1.0 and higher, and is the default for releases of Amazon EMR earlier than 5.1.0.
Available only in Amazon EMR releases 5.7.0 and later. The ID of a custom Amazon\n EBS-backed Linux AMI. If specified, Amazon EMR uses this AMI when it launches\n cluster Amazon EC2 instances. For more information about custom AMIs in Amazon EMR, see Using a Custom AMI in the\n Amazon EMR Management Guide. If omitted, the cluster\n uses the base Linux AMI for the ReleaseLabel specified. For Amazon EMR\n releases 2.x and 3.x, use AmiVersion instead.
For information about creating a custom AMI, see Creating an Amazon EBS-Backed Linux AMI in the Amazon Elastic Compute Cloud User Guide for Linux\n Instances. For information about finding an AMI ID, see Finding a Linux\n AMI.
" + "smithy.api#documentation": "Available only in Amazon EMR releases 5.7.0 and higher. The ID of a custom\n Amazon EBS-backed Linux AMI. If specified, Amazon EMR uses this AMI when it\n launches cluster Amazon EC2 instances. For more information about custom AMIs in\n Amazon EMR, see Using a Custom AMI in the\n Amazon EMR Management Guide. If omitted, the cluster\n uses the base Linux AMI for the ReleaseLabel specified. For Amazon EMR\n releases 2.x and 3.x, use AmiVersion instead.
For information about creating a custom AMI, see Creating an Amazon EBS-Backed Linux AMI in the Amazon Elastic Compute Cloud User Guide for Linux\n Instances. For information about finding an AMI ID, see Finding a Linux\n AMI.
" } }, "EbsRootVolumeSize": { "target": "com.amazonaws.emr#Integer", "traits": { - "smithy.api#documentation": "The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is\n used for each Amazon EC2 instance. Available in Amazon EMR releases 4.x and\n later.
" + "smithy.api#documentation": "The size, in GiB, of the Amazon EBS root device volume for the Linux AMI that\n each Amazon EC2 instance uses. Available in Amazon EMR releases 4.x and\n higher.
" } }, "RepoUpgradeOnBoot": { @@ -8567,10 +8579,22 @@ "traits": { "smithy.api#documentation": "Specifies a particular Amazon Linux release for all nodes in a cluster launch RunJobFlow\n request. If a release is not specified, Amazon EMR uses the latest validated Amazon\n Linux release for cluster launch.
" } + }, + "EbsRootVolumeIops": { + "target": "com.amazonaws.emr#Integer", + "traits": { + "smithy.api#documentation": "The IOPS for the Amazon EBS root device volume for the Linux AMI that each\n Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0 and\n higher.
" + } + }, + "EbsRootVolumeThroughput": { + "target": "com.amazonaws.emr#Integer", + "traits": { + "smithy.api#documentation": "The throughput, in MiB/s, of the Amazon EBS root device volume for the Linux AMI\n that each Amazon EC2 instance uses. Available in Amazon EMR releases 6.15.0\n and higher.
" + } } }, "traits": { - "smithy.api#documentation": "Input to the RunJobFlow operation.
", + "smithy.api#documentation": "Input to the RunJobFlow operation.
", "smithy.api#input": {} } }, @@ -9087,12 +9111,12 @@ "AllocationStrategy": { "target": "com.amazonaws.emr#SpotProvisioningAllocationStrategy", "traits": { - "smithy.api#documentation": "Specifies the strategy to use in launching Spot Instance fleets. Currently, the only\n option is capacity-optimized (the default), which launches instances from Spot Instance\n pools with optimal capacity for the number of instances that are launching.
" + "smithy.api#documentation": "Specifies one of the following strategies to launch Spot Instance fleets:\n price-capacity-optimized, capacity-optimized,\n lowest-price, or diversified. For more information on the\n provisioning strategies, see Allocation strategies\n for Spot Instances in the Amazon EC2 User Guide for Linux\n Instances.
When you launch a Spot Instance fleet with the old console, it automatically launches\n with the capacity-optimized strategy. You can't change the allocation\n strategy from the old console.
The launch specification for Spot Instances in the instance fleet, which determines the\n defined duration, provisioning timeout behavior, and allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and later, excluding 5.0.x versions. Spot Instance allocation strategy is\n available in Amazon EMR releases 5.12.1 and later.
\nSpot Instances with a defined duration (also known as Spot blocks) are no longer\n available to new customers from July 1, 2021. For customers who have previously used the\n feature, we will continue to support Spot Instances with a defined duration until\n December 31, 2022.
\nThe launch specification for Spot Instances in the instance fleet, which determines the\n defined duration, provisioning timeout behavior, and allocation strategy.
\nThe instance fleet configuration is available only in Amazon EMR releases\n 4.8.0 and higher, excluding 5.0.x versions. Spot Instance allocation strategy is\n available in Amazon EMR releases 5.12.1 and higher.
\nSpot Instances with a defined duration (also known as Spot blocks) are no longer\n available to new customers from July 1, 2021. For customers who have previously used the\n feature, we will continue to support Spot Instances with a defined duration until\n December 31, 2022.
\nThe amount of memory that is available to Amazon EMR from the SupportedInstanceType. The kernel and hypervisor\n software consume some memory, so this value might be lower than the overall memory for the\n instance type.
The amount of memory that is available to Amazon EMR from the\n SupportedInstanceType. The kernel and hypervisor software consume some\n memory, so this value might be lower than the overall memory for the instance type.