The target resource type of the recommendation preference to delete.
\nThe Ec2Instance option encompasses standalone instances and instances\n that are part of Auto Scaling groups. The AutoScalingGroup option\n encompasses only instances that are part of an Auto Scaling group.
The target resource type of the recommendation preference to delete.
\nThe Ec2Instance option encompasses standalone instances and instances\n that are part of Auto Scaling groups. The AutoScalingGroup option\n encompasses only instances that are part of an Auto Scaling group.
The valid values for this parameter are Ec2Instance and\n AutoScalingGroup.
The target resource type of the recommendation preference for which to return\n preferences.
\nThe Ec2Instance option encompasses standalone instances and instances\n that are part of Auto Scaling groups. The AutoScalingGroup option\n encompasses only instances that are part of an Auto Scaling group.
The target resource type of the recommendation preference for which to return\n preferences.
\nThe Ec2Instance option encompasses standalone instances and instances\n that are part of Auto Scaling groups. The AutoScalingGroup option\n encompasses only instances that are part of an Auto Scaling group.
The valid values for this parameter are Ec2Instance and\n AutoScalingGroup.
The target resource type of the recommendation preference to create.
\nThe Ec2Instance option encompasses standalone instances and instances\n that are part of Auto Scaling groups. The AutoScalingGroup option\n encompasses only instances that are part of an Auto Scaling group.
The target resource type of the recommendation preference to create.
\nThe Ec2Instance option encompasses standalone instances and instances\n that are part of Auto Scaling groups. The AutoScalingGroup option\n encompasses only instances that are part of an Auto Scaling group.
The valid values for this parameter are Ec2Instance and\n AutoScalingGroup.
A binary representation of the UEFI variable store. Only non-volatile variables are\n stored. This is a base64 encoded and zlib compressed binary value that must be properly\n encoded.
\nWhen you use register-image\n to create an AMI, you can create an exact copy of your variable store by passing the UEFI data in the UefiData\n parameter. You can modify the UEFI data by using the python-uefivars tool\n on GitHub. You can use the tool to convert the UEFI data into a human-readable format (JSON), which you can \n inspect and modify, and then convert back into the binary format to use with register-image.
For more information, see UEFI Secure Boot in the\n Amazon EC2 User Guide.
" + } + }, + "com.amazonaws.ec2#GetInstanceUefiDataRequest": { + "type": "structure", + "members": { + "InstanceId": { + "target": "com.amazonaws.ec2#InstanceId", + "traits": { + "smithy.api#documentation": "The ID of the instance from which to retrieve the UEFI data.
", + "smithy.api#required": {}, + "smithy.api#xmlName": "InstanceId" + } + }, + "DryRun": { + "target": "com.amazonaws.ec2#Boolean", + "traits": { + "smithy.api#documentation": "Checks whether you have the required permissions for the action, without actually making the request, \n and provides an error response. If you have the required permissions, the error response is DryRunOperation. \n Otherwise, it is UnauthorizedOperation.
The ID of the instance from which to retrieve the UEFI data.
", + "smithy.api#xmlName": "instanceId" + } + }, + "UefiData": { + "target": "com.amazonaws.ec2#String", + "traits": { + "aws.protocols#ec2QueryName": "UefiData", + "smithy.api#documentation": "Base64 representation of the non-volatile UEFI variable store.
", + "smithy.api#xmlName": "uefiData" + } + } + } + }, "com.amazonaws.ec2#GetIpamAddressHistory": { "type": "operation", "input": { @@ -40869,6 +40924,14 @@ "smithy.api#xmlName": "bootMode" } }, + "TpmSupport": { + "target": "com.amazonaws.ec2#TpmSupportValues", + "traits": { + "aws.protocols#ec2QueryName": "TpmSupport", + "smithy.api#documentation": "If the image is configured for NitroTPM support, the value is v2.0. \n For more information, see NitroTPM in the\n Amazon Elastic Compute Cloud User Guide.
If the image is configured for NitroTPM support, the value is v2.0.
Base64 representation of the non-volatile UEFI variable store. To retrieve the UEFI data,\n use the GetInstanceUefiData command. You can inspect and modify the UEFI data by using the\n python-uefivars tool on\n GitHub. For more information, see UEFI Secure Boot in the\n Amazon Elastic Compute Cloud User Guide.
", + "smithy.api#xmlName": "uefiData" + } + }, "LastLaunchedTime": { "target": "com.amazonaws.ec2#AttributeValue", "traits": { @@ -41006,6 +41085,14 @@ "value": "bootMode", "name": "bootMode" }, + { + "value": "tpmSupport", + "name": "tpmSupport" + }, + { + "value": "uefiData", + "name": "uefiData" + }, { "value": "lastLaunchedTime", "name": "lastLaunchedTime" @@ -42887,6 +42974,14 @@ "smithy.api#xmlName": "ipv6Address" } }, + "TpmSupport": { + "target": "com.amazonaws.ec2#String", + "traits": { + "aws.protocols#ec2QueryName": "TpmSupport", + "smithy.api#documentation": "If the instance is configured for NitroTPM support, the value is v2.0.\n For more information, see NitroTPM in the\n Amazon EC2 User Guide.
The boot mode of the AMI. For more information, see Boot modes in the\n Amazon Elastic Compute Cloud User Guide.
" } + }, + "TpmSupport": { + "target": "com.amazonaws.ec2#TpmSupportValues", + "traits": { + "smithy.api#documentation": "Set to v2.0 to enable Trusted Platform Module (TPM) support. For more\n information, see NitroTPM in the Amazon Elastic Compute Cloud User Guide.
Base64 representation of the non-volatile UEFI variable store. To retrieve the UEFI data,\n use the GetInstanceUefiData command. You can inspect and modify the UEFI data by using the\n python-uefivars tool on\n GitHub. For more information, see UEFI Secure Boot in the\n Amazon Elastic Compute Cloud User Guide.
" + } } }, "traits": { @@ -72369,6 +72476,15 @@ } } }, + "com.amazonaws.ec2#StringType": { + "type": "string", + "traits": { + "smithy.api#length": { + "min": 0, + "max": 64000 + } + } + }, "com.amazonaws.ec2#Subnet": { "type": "structure", "members": { @@ -73656,6 +73772,17 @@ "smithy.api#documentation": "The minimum and maximum amount of total local storage, in GB.
" } }, + "com.amazonaws.ec2#TpmSupportValues": { + "type": "string", + "traits": { + "smithy.api#enum": [ + { + "value": "v2.0", + "name": "v2_0" + } + ] + } + }, "com.amazonaws.ec2#TrafficDirection": { "type": "string", "traits": { diff --git a/codegen/sdk-codegen/aws-models/eks.json b/codegen/sdk-codegen/aws-models/eks.json index 552940ff74a..4c3a3d4e7de 100644 --- a/codegen/sdk-codegen/aws-models/eks.json +++ b/codegen/sdk-codegen/aws-models/eks.json @@ -56,6 +56,14 @@ { "value": "BOTTLEROCKET_x86_64", "name": "BOTTLEROCKET_x86_64" + }, + { + "value": "BOTTLEROCKET_ARM_64_NVIDIA", + "name": "BOTTLEROCKET_ARM_64_NVIDIA" + }, + { + "value": "BOTTLEROCKET_x86_64_NVIDIA", + "name": "BOTTLEROCKET_x86_64_NVIDIA" } ] } @@ -1381,13 +1389,13 @@ "diskSize": { "target": "com.amazonaws.eks#BoxedInteger", "traits": { - "smithy.api#documentation": "The root device disk size (in GiB) for your node group instances. The default disk\n size is 20 GiB. If you specify launchTemplate, then don't specify diskSize,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The root device disk size (in GiB) for your node group instances. The default disk\n size is 20 GiB. If you specify launchTemplate, then don't specify diskSize,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The subnets to use for the Auto Scaling group that is created for your node group.\n If you specify launchTemplate, then don't specify \n SubnetId\n in your launch template, or the node group \n deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The subnets to use for the Auto Scaling group that is created for your node group.\n If you specify launchTemplate, then don't specify \n SubnetId\n in your launch template, or the node group \n deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The AMI type for your node group. GPU instance types should use the\n AL2_x86_64_GPU AMI type. Non-GPU instances should use the\n AL2_x86_64 AMI type. Arm instances should use the\n AL2_ARM_64 AMI type. All types use the Amazon EKS optimized\n Amazon Linux 2 AMI. If you specify launchTemplate, and your launch template uses a custom AMI,\n then don't specify amiType, or the node group deployment\n will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The AMI type for your node group. GPU instance types should use the\n AL2_x86_64_GPU AMI type. Non-GPU instances should use the\n AL2_x86_64 AMI type. Arm instances should use the\n AL2_ARM_64 AMI type. All types use the Amazon EKS optimized\n Amazon Linux 2 AMI. If you specify launchTemplate, and your launch template uses a custom AMI,\n then don't specify amiType, or the node group deployment\n will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The remote access (SSH) configuration to use with your node group. If you specify launchTemplate,\n then don't specify remoteAccess, or the node group deployment\n will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The remote access (SSH) configuration to use with your node group. If you specify launchTemplate,\n then don't specify remoteAccess, or the node group deployment\n will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The Amazon Resource Name (ARN) of the IAM role to associate with your node group. The\n Amazon EKS worker node kubelet daemon makes calls to Amazon Web Services APIs on your behalf. Nodes receive permissions for these API calls\n through an IAM instance profile and associated policies. Before you can\n launch nodes and register them into a cluster, you must create an IAM\n role for those nodes to use when they are launched. For more information, see Amazon EKS node IAM role in the\n \n Amazon EKS User Guide\n . If you specify launchTemplate, then don't specify \n \n IamInstanceProfile\n in your launch template,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The Amazon Resource Name (ARN) of the IAM role to associate with your node group. The\n Amazon EKS worker node kubelet daemon makes calls to Amazon Web Services APIs on your behalf. Nodes receive permissions for these API calls\n through an IAM instance profile and associated policies. Before you can\n launch nodes and register them into a cluster, you must create an IAM\n role for those nodes to use when they are launched. For more information, see Amazon EKS node IAM role in the\n \n Amazon EKS User Guide\n . If you specify launchTemplate, then don't specify \n \n IamInstanceProfile\n in your launch template,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The Kubernetes taints to be applied to the nodes in the node group.
" + "smithy.api#documentation": "The Kubernetes taints to be applied to the nodes in the node group. For more information, see Node taints on managed node groups.
" } }, "tags": { @@ -1462,13 +1470,13 @@ "version": { "target": "com.amazonaws.eks#String", "traits": { - "smithy.api#documentation": "The Kubernetes version to use for your managed nodes. By default, the Kubernetes\n version of the cluster is used, and this is the only accepted specified value.\n If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify version,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The Kubernetes version to use for your managed nodes. By default, the Kubernetes\n version of the cluster is used, and this is the only accepted specified value.\n If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify version,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The AMI version of the Amazon EKS optimized AMI to use with your node group.\n By default, the latest available AMI version for the node group's current Kubernetes\n version is used. For more information, see Amazon EKS optimized Amazon Linux 2 AMI versions in the Amazon EKS User Guide.\n If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify releaseVersion,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The AMI version of the Amazon EKS optimized AMI to use with your node group.\n By default, the latest available AMI version for the node group's current Kubernetes\n version is used. For more information, see Amazon EKS optimized Amazon Linux 2 AMI versions in the Amazon EKS User Guide.\n If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify releaseVersion,\n or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
Returns descriptive information about an update against your Amazon EKS\n cluster or associated managed node group.
\nWhen the status of the update is Succeeded, the update is complete. If an\n update fails, the status is Failed, and an error detail explains the reason\n for the failure.
Returns descriptive information about an update against your Amazon EKS\n cluster or associated managed node group or Amazon EKS add-on.
\nWhen the status of the update is Succeeded, the update is complete. If an\n update fails, the status is Failed, and an error detail explains the reason\n for the failure.
The name of the Amazon EKS node group associated with the update.
", + "smithy.api#documentation": "The name of the Amazon EKS node group associated with the update. This\n parameter is required if the update is a node group update.
", "smithy.api#httpQuery": "nodegroupName" } }, "addonName": { "target": "com.amazonaws.eks#String", "traits": { - "smithy.api#documentation": "The name of the add-on. The name must match one of the names returned by \n ListAddons\n .
The name of the add-on. The name must match one of the names returned by \n ListAddons\n . This parameter is required if the update is an add-on update.
The type of the identity provider configuration.
", + "smithy.api#documentation": "The type of the identity provider configuration. The only type available is\n oidc.
A brief description of the error.
\n\n AccessDenied: Amazon EKS or one or\n more of your managed nodes is failing to authenticate or authorize with your\n Kubernetes cluster API server.
\n\n AsgInstanceLaunchFailures: Your Auto Scaling group is experiencing failures while attempting to launch\n instances.
\n\n AutoScalingGroupNotFound: We couldn't find\n the Auto Scaling group associated with the managed node group. You may be\n able to recreate an Auto Scaling group with the same settings to\n recover.
\n\n ClusterUnreachable: Amazon EKS or one\n or more of your managed nodes is unable to to communicate with your Kubernetes\n cluster API server. This can happen if there are network disruptions or if API\n servers are timing out processing requests.
\n\n Ec2LaunchTemplateNotFound: We couldn't find\n the Amazon EC2 launch template for your managed node group. You may be\n able to recreate a launch template with the same settings to recover.
\n\n Ec2LaunchTemplateVersionMismatch: The Amazon EC2 launch template version for your managed node group does not\n match the version that Amazon EKS created. You may be able to revert to\n the version that Amazon EKS created to recover.
\n\n Ec2SecurityGroupDeletionFailure: We could not\n delete the remote access security group for your managed node group. Remove any\n dependencies from the security group.
\n\n Ec2SecurityGroupNotFound: We couldn't find\n the cluster security group for the cluster. You must recreate your\n cluster.
\n\n Ec2SubnetInvalidConfiguration: One or more\n Amazon EC2 subnets specified for a node group do not automatically\n assign public IP addresses to instances launched into it. If you want your\n instances to be assigned a public IP address, then you need to enable the\n auto-assign public IP address setting for the subnet. See\n Modifying\n the public IPv4 addressing attribute for your subnet in the Amazon\n VPC User Guide.
\n IamInstanceProfileNotFound: We couldn't find\n the IAM instance profile for your managed node group. You may be\n able to recreate an instance profile with the same settings to recover.
\n\n IamNodeRoleNotFound: We couldn't find the\n IAM role for your managed node group. You may be able to\n recreate an IAM role with the same settings to recover.
\n\n InstanceLimitExceeded: Your Amazon Web Services account is unable to launch any more instances of the specified instance\n type. You may be able to request an Amazon EC2 instance limit increase\n to recover.
\n\n InsufficientFreeAddresses: One or more of the\n subnets associated with your managed node group does not have enough available\n IP addresses for new nodes.
\n\n InternalFailure: These errors are usually\n caused by an Amazon EKS server-side issue.
\n\n NodeCreationFailure: Your launched instances\n are unable to register with your Amazon EKS cluster. Common causes of this failure\n are insufficient node IAM role\n permissions or lack of outbound internet access for the nodes.
\nA brief description of the error.
\n\n AccessDenied: Amazon EKS or one or\n more of your managed nodes is failing to authenticate or authorize with your\n Kubernetes cluster API server.
\n\n AsgInstanceLaunchFailures: Your Auto Scaling group is experiencing failures while attempting to launch\n instances.
\n\n AutoScalingGroupNotFound: We couldn't find\n the Auto Scaling group associated with the managed node group. You may be\n able to recreate an Auto Scaling group with the same settings to\n recover.
\n\n ClusterUnreachable: Amazon EKS or one\n or more of your managed nodes is unable to to communicate with your Kubernetes\n cluster API server. This can happen if there are network disruptions or if API\n servers are timing out processing requests.
\n\n Ec2LaunchTemplateNotFound: We couldn't find\n the Amazon EC2 launch template for your managed node group. You may be\n able to recreate a launch template with the same settings to recover.
\n\n Ec2LaunchTemplateVersionMismatch: The Amazon EC2 launch template version for your managed node group does not\n match the version that Amazon EKS created. You may be able to revert to\n the version that Amazon EKS created to recover.
\n\n Ec2SecurityGroupDeletionFailure: We could not\n delete the remote access security group for your managed node group. Remove any\n dependencies from the security group.
\n\n Ec2SecurityGroupNotFound: We couldn't find\n the cluster security group for the cluster. You must recreate your\n cluster.
\n\n Ec2SubnetInvalidConfiguration: One or more\n Amazon EC2 subnets specified for a node group do not automatically\n assign public IP addresses to instances launched into it. If you want your\n instances to be assigned a public IP address, then you need to enable the\n auto-assign public IP address setting for the subnet. See\n Modifying\n the public IPv4 addressing attribute for your subnet in the\n Amazon VPC User Guide.
\n IamInstanceProfileNotFound: We couldn't find\n the IAM instance profile for your managed node group. You may be\n able to recreate an instance profile with the same settings to recover.
\n\n IamNodeRoleNotFound: We couldn't find the\n IAM role for your managed node group. You may be able to\n recreate an IAM role with the same settings to recover.
\n\n InstanceLimitExceeded: Your Amazon Web Services account is unable to launch any more instances of the specified instance\n type. You may be able to request an Amazon EC2 instance limit increase\n to recover.
\n\n InsufficientFreeAddresses: One or more of the\n subnets associated with your managed node group does not have enough available\n IP addresses for new nodes.
\n\n InternalFailure: These errors are usually\n caused by an Amazon EKS server-side issue.
\n\n NodeCreationFailure: Your launched instances\n are unable to register with your Amazon EKS cluster. Common causes of this failure\n are insufficient node IAM role\n permissions or lack of outbound internet access for the nodes.
\nSpecify which IP version is used to assign Kubernetes Pod and Service IP addresses. If\n you don't specify a value, ipv4 is used by default. You can only specify an\n IP family when you create a cluster and can't change this value once the cluster is\n created. If you specify ipv6, the VPC and subnets that you specify for\n cluster creation must have both IPv4 and IPv6 CIDR blocks assigned to them.
You can only specify ipv6 for 1.21 and later clusters that use version\n 1.10.0 or later of the Amazon VPC CNI add-on. If you specify ipv6, then ensure\n that your VPC meets the requirements and that you're familiar with the considerations\n listed in Assigning\n IPv6 addresses to Pods and Services in the Amazon EKS User Guide. If\n you specify ipv6, Kubernetes assigns Service and Pod addresses from the\n unique local address range (fc00::/7). You can't specify a custom IPv6 CIDR\n block.
Specify which IP family is used to assign Kubernetes pod and service IP addresses. If\n you don't specify a value, ipv4 is used by default. You can only specify an\n IP family when you create a cluster and can't change this value once the cluster is\n created. If you specify ipv6, the VPC and subnets that you specify for\n cluster creation must have both IPv4 and IPv6 CIDR blocks assigned to them. You can't\n specify ipv6 for clusters in China Regions.
You can only specify ipv6 for 1.21 and later clusters that use version\n 1.10.1 or later of the Amazon VPC CNI add-on. If you specify ipv6, then ensure\n that your VPC meets the requirements listed in the considerations listed in Assigning IPv6\n addresses to pods and services in the Amazon EKS User Guide.\n Kubernetes assigns services IPv6 addresses from the unique local address range\n (fc00::/7). You can't specify a custom IPv6 CIDR block. Pod addresses are assigned from\n the subnet's IPv6 CIDR.
The CIDR block that Kubernetes Pod and Service IP addresses are assigned from.\n Kubernetes assigns addresses from an IPv4 CIDR block assigned to a subnet that the node\n is in. If you didn't specify a CIDR block when you created the cluster, then Kubernetes\n assigns addresses from either the 10.100.0.0/16 or 172.20.0.0/16 CIDR blocks. If this\n was specified, then it was specified when the cluster was created and it can't be\n changed.
" + "smithy.api#documentation": "The CIDR block that Kubernetes pod and service IP addresses are assigned from.\n Kubernetes assigns addresses from an IPv4 CIDR block assigned to a subnet that the node\n is in. If you didn't specify a CIDR block when you created the cluster, then Kubernetes\n assigns addresses from either the 10.100.0.0/16 or 172.20.0.0/16 CIDR blocks. If this\n was specified, then it was specified when the cluster was created and it can't be\n changed.
" } }, "serviceIpv6Cidr": { "target": "com.amazonaws.eks#String", "traits": { - "smithy.api#documentation": "The CIDR block that Kubernetes Pod and Service IP addresses are assigned from if you\n created a 1.21 or later cluster with version 1.10.0 or later of the Amazon VPC CNI add-on and\n specified ipv6 for ipFamily when you\n created the cluster. Kubernetes assigns addresses from the unique local address range\n (fc00::/7).
The CIDR block that Kubernetes pod and service IP addresses are assigned from if you\n created a 1.21 or later cluster with version 1.10.1 or later of the Amazon VPC CNI add-on and\n specified ipv6 for ipFamily when you\n created the cluster. Kubernetes assigns service addresses from the unique local address\n range (fc00::/7) because you can't specify a custom IPv6 CIDR block when\n you create the cluster.
The IP family used to assign Kubernetes Pod and Service IP addresses. The IP family is\n always ipv4, unless you have a 1.21 or later cluster running\n version 1.10.0 or later of the Amazon VPC CNI add-on and specified ipv6 when you\n created the cluster.
The IP family used to assign Kubernetes pod and service IP addresses. The IP family is\n always ipv4, unless you have a 1.21 or later cluster running\n version 1.10.1 or later of the Amazon VPC CNI add-on and specified ipv6 when you\n created the cluster.
An object representing a node group launch template specification. The launch template\n cannot include \n SubnetId\n , \n IamInstanceProfile\n , \n RequestSpotInstances\n , \n HibernationOptions\n , or \n TerminateInstances\n , or the node group deployment or\n update will fail. For more information about launch templates, see \n CreateLaunchTemplate\n in the Amazon EC2 API\n Reference. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
Specify either name or id, but not both.
An object representing a node group launch template specification. The launch template\n cannot include \n SubnetId\n , \n IamInstanceProfile\n , \n RequestSpotInstances\n , \n HibernationOptions\n , or \n TerminateInstances\n , or the node group deployment or\n update will fail. For more information about launch templates, see \n CreateLaunchTemplate\n in the Amazon EC2 API\n Reference. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
Specify either name or id, but not both.
The Kubernetes taints to be applied to the nodes in the node group when they are\n created. Effect is one of No_Schedule, Prefer_No_Schedule, or\n No_Execute. Kubernetes taints can be used together with tolerations to\n control how workloads are scheduled to your nodes.
The Kubernetes taints to be applied to the nodes in the node group when they are\n created. Effect is one of No_Schedule, Prefer_No_Schedule, or\n No_Execute. Kubernetes taints can be used together with tolerations to\n control how workloads are scheduled to your nodes. For more information, see Node taints on managed node groups.
Required resources (such as Service Linked Roles) were created and are still propagating. Retry later.
", + "smithy.api#documentation": "Required resources (such as service-linked roles) were created and are still propagating. Retry later.
", "smithy.api#error": "client", "smithy.api#httpError": 428 } @@ -4722,7 +4730,7 @@ } }, "traits": { - "smithy.api#documentation": "A property that allows a node to repel a set of pods.
" + "smithy.api#documentation": "A property that allows a node to repel a set of pods. For more information, see Node taints on managed node groups.
" } }, "com.amazonaws.eks#TaintEffect": { @@ -5197,7 +5205,7 @@ "taints": { "target": "com.amazonaws.eks#UpdateTaintsPayload", "traits": { - "smithy.api#documentation": "The Kubernetes taints to be applied to the nodes in the node group after the\n update.
" + "smithy.api#documentation": "The Kubernetes taints to be applied to the nodes in the node group after the\n update. For more information, see Node taints on managed node groups.
" } }, "scalingConfig": { @@ -5288,13 +5296,13 @@ "version": { "target": "com.amazonaws.eks#String", "traits": { - "smithy.api#documentation": "The Kubernetes version to update to. If no version is specified, then the Kubernetes\n version of the node group does not change. You can specify the Kubernetes version of the\n cluster to update the node group to the latest AMI version of the cluster's Kubernetes\n version. If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify \n version, or the node group update will fail.\n For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The Kubernetes version to update to. If no version is specified, then the Kubernetes\n version of the node group does not change. You can specify the Kubernetes version of the\n cluster to update the node group to the latest AMI version of the cluster's Kubernetes\n version. If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify \n version, or the node group update will fail.\n For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The AMI version of the Amazon EKS optimized AMI to use for the update. By\n default, the latest available AMI version for the node group's Kubernetes version is\n used. For more information, see Amazon EKS optimized Amazon Linux 2 AMI versions in the Amazon EKS User Guide.\n If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify releaseVersion,\n or the node group update will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
The AMI version of the Amazon EKS optimized AMI to use for the update. By\n default, the latest available AMI version for the node group's Kubernetes version is\n used. For more information, see Amazon EKS optimized Amazon Linux 2 AMI versions in the Amazon EKS User Guide.\n If you specify launchTemplate, and your launch template uses a custom AMI, then don't specify releaseVersion,\n or the node group update will fail. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.
An object representing the details of an update to a taints payload.
" + "smithy.api#documentation": "An object representing the details of an update to a taints payload. For more information, see Node taints on managed node groups.
" } }, "com.amazonaws.eks#UpdateType": { diff --git a/codegen/sdk-codegen/aws-models/emr.json b/codegen/sdk-codegen/aws-models/emr.json index 4e9c8424622..7770d7ca073 100644 --- a/codegen/sdk-codegen/aws-models/emr.json +++ b/codegen/sdk-codegen/aws-models/emr.json @@ -69,7 +69,7 @@ } ], "traits": { - "smithy.api#documentation": "Adds an instance fleet to a running cluster.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x.
\nAdds an instance fleet to a running cluster.
\nThe instance fleet configuration is available only in Amazon EMR versions\n 4.8.0 and later, excluding 5.0.x.
\nAddJobFlowSteps adds new steps to a running cluster. A maximum of 256 steps are allowed\n 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 SSH to connect to the master node and submitting queries\n directly to the software running on the master node, such as Hive and Hadoop. For more\n information on how to do this, see Add More than 256 Steps to a\n Cluster in the Amazon EMR Management Guide.
\nA step specifies the location of a JAR file stored either on the master node of the\n cluster or in Amazon S3. Each step is performed by the main function of the main class of\n the JAR file. The main class can be specified either in the manifest of the JAR or by using\n the MainFunction parameter of the step.
\nAmazon EMR executes each step in the order listed. For a step to be considered complete,\n the main function must exit with a zero exit code and all Hadoop jobs started while the\n step was running must have completed and run successfully.
\nYou can only add steps to a cluster that is in one of the following states: STARTING,\n BOOTSTRAPPING, RUNNING, or WAITING.
\nThe string values passed into HadoopJarStep object cannot exceed a total of 10240 characters.
AddJobFlowSteps adds new steps to a running cluster. A maximum of 256 steps are allowed\n 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 SSH to connect to the master node and submitting queries\n directly to the software running on the master node, such as Hive and Hadoop. For more\n information on how to do this, see Add More than 256 Steps to a\n Cluster in the Amazon EMR Management Guide.
\nA step specifies the location of a JAR file stored either on the master node of the\n cluster or in Amazon S3. Each step is performed by the main function of the main\n class of the JAR file. The main class can be specified either in the manifest of the JAR or\n by using the MainFunction parameter of the step.
\nAmazon EMR executes each step in the order listed. For a step to be considered\n complete, the main function must exit with a zero exit code and all Hadoop jobs started\n while the step was running must have completed and run successfully.
\nYou can only add steps to a cluster that is in one of the following states: STARTING,\n BOOTSTRAPPING, RUNNING, or WAITING.
\nThe string values passed into HadoopJarStep object cannot exceed a total\n of 10240 characters.
Adds tags to an Amazon EMR resource, such as a cluster or an Amazon EMR Studio. Tags make it easier to associate resources in\n various ways, such as grouping clusters to track your Amazon EMR resource allocation costs.\n For more information, see Tag Clusters.
" + "smithy.api#documentation": "Adds tags to an Amazon EMR resource, such as a cluster or an Amazon EMR\n Studio. Tags make it easier to associate resources in various ways, such as grouping\n clusters to track your Amazon EMR resource allocation costs. For more information,\n see Tag\n Clusters.
" } }, "com.amazonaws.emr#AddTagsInput": { @@ -265,13 +265,13 @@ "Tags": { "target": "com.amazonaws.emr#TagList", "traits": { - "smithy.api#documentation": "A list of tags to associate with a resource. Tags are\n user-defined key-value pairs that consist of a required key string with a maximum of 128\n characters, and an optional value string with a maximum of 256 characters.
", + "smithy.api#documentation": "A list of tags to associate with a resource. Tags are user-defined key-value pairs that\n consist of a required key string with a maximum of 128 characters, and an optional value\n string with a maximum of 256 characters.
", "smithy.api#required": {} } } }, "traits": { - "smithy.api#documentation": "This input identifies an Amazon EMR resource and a list of tags to attach.
" + "smithy.api#documentation": "This input identifies an Amazon EMR resource and a list of tags to\n attach.
" } }, "com.amazonaws.emr#AddTagsOutput": { @@ -329,7 +329,7 @@ } }, "traits": { - "smithy.api#documentation": "With Amazon EMR release version 4.0 and later, the only accepted parameter is the\n application name. To pass arguments to applications, you use configuration classifications\n specified using configuration JSON objects. For more information, see Configuring\n Applications.
\nWith earlier Amazon EMR releases, the application is any Amazon or third-party software\n that you can add to the cluster. This structure contains a list of strings that indicates\n the software to use with the cluster and accepts a user argument list. Amazon EMR accepts\n and forwards the argument list to the corresponding installation script as bootstrap action\n argument.
" + "smithy.api#documentation": "With 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.
" } }, "com.amazonaws.emr#ApplicationList": { @@ -381,7 +381,7 @@ } }, "traits": { - "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. An automatic scaling policy defines how an instance group dynamically\n adds and terminates EC2 instances in response to the value of a CloudWatch metric. See\n PutAutoScalingPolicy.
" + "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. An automatic scaling policy defines how an instance group\n dynamically adds and terminates EC2 instances in response to the value of a CloudWatch\n metric. See PutAutoScalingPolicy.
" } }, "com.amazonaws.emr#AutoScalingPolicyDescription": { @@ -407,7 +407,7 @@ } }, "traits": { - "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. The automatic scaling policy defines how an instance group dynamically\n adds and terminates EC2 instances in response to the value of a CloudWatch metric. See\n PutAutoScalingPolicy.
" + "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. The automatic scaling policy defines how an instance group\n dynamically adds and terminates EC2 instances in response to the value of a CloudWatch\n metric. See PutAutoScalingPolicy.
" } }, "com.amazonaws.emr#AutoScalingPolicyState": { @@ -506,12 +506,12 @@ "IdleTimeout": { "target": "com.amazonaws.emr#Long", "traits": { - "smithy.api#documentation": "Specifies the amount of idle time in seconds after which the cluster automatically terminates. You can specify a minimum of 60 seconds and a maximum of 604800 seconds (seven days).
" + "smithy.api#documentation": "Specifies the amount of idle time in seconds after which the cluster automatically\n terminates. You can specify a minimum of 60 seconds and a maximum of 604800 seconds (seven\n days).
" } } }, "traits": { - "smithy.api#documentation": "An auto-termination policy for an Amazon EMR cluster. An auto-termination policy defines the amount of idle time in seconds after which a cluster automatically terminates. For alternative cluster termination options, see Control cluster termination.
" + "smithy.api#documentation": "An auto-termination policy for an Amazon EMR cluster. An auto-termination policy\n defines the amount of idle time in seconds after which a cluster automatically terminates.\n For alternative cluster termination options, see Control cluster\n termination.
" } }, "com.amazonaws.emr#BlockPublicAccessConfiguration": { @@ -520,14 +520,14 @@ "BlockPublicSecurityGroupRules": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "Indicates whether Amazon EMR block public access is enabled (true) or\n disabled (false). By default, the value is false for accounts\n that have created EMR clusters before July 2019. For accounts created after this, the\n default is true.
Indicates whether Amazon EMR block public access is enabled (true)\n or disabled (false). By default, the value is false for accounts\n that have created EMR clusters before July 2019. For accounts created after this, the\n default is true.
Specifies ports and port ranges that are permitted to have security group rules that\n allow inbound traffic from all public sources. For example, if Port 23 (Telnet) is\n specified for PermittedPublicSecurityGroupRuleRanges, Amazon EMR allows\n cluster creation if a security group associated with the cluster has a rule that allows\n inbound traffic on Port 23 from IPv4 0.0.0.0/0 or IPv6 port ::/0 as the source.
By default, Port 22, which is used for SSH access to the cluster EC2 instances, is in\n the list of PermittedPublicSecurityGroupRuleRanges.
Specifies ports and port ranges that are permitted to have security group rules that\n allow inbound traffic from all public sources. For example, if Port 23 (Telnet) is\n specified for PermittedPublicSecurityGroupRuleRanges, Amazon EMR\n allows cluster creation if a security group associated with the cluster has a rule that\n allows inbound traffic on Port 23 from IPv4 0.0.0.0/0 or IPv6 port ::/0 as the\n source.
By default, Port 22, which is used for SSH access to the cluster EC2 instances, is in\n the list of PermittedPublicSecurityGroupRuleRanges.
A configuration for Amazon EMR block public access. When\n BlockPublicSecurityGroupRules is set to true, Amazon EMR\n prevents cluster creation if one of the cluster's security groups has a rule that allows\n inbound traffic from 0.0.0.0/0 or ::/0 on a port, unless the port is specified as an\n exception using PermittedPublicSecurityGroupRuleRanges.
A configuration for Amazon EMR block public access. When\n BlockPublicSecurityGroupRules is set to true, Amazon EMR prevents cluster creation if one of the cluster's security groups has a rule that allows\n inbound traffic from 0.0.0.0/0 or ::/0 on a port, unless the port is specified as an\n exception using PermittedPublicSecurityGroupRuleRanges.
Cancels a pending step or steps in a running cluster. Available only in Amazon EMR\n 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 Amazon EMR versions 5.28.0 and later, 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.
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 versions 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.
Specification of the status of a CancelSteps request. Available only in Amazon EMR\n 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 later, excluding version 5.0.0.
" } }, "com.amazonaws.emr#CancelStepsInfoList": { @@ -837,19 +837,19 @@ "InstanceCollectionType": { "target": "com.amazonaws.emr#InstanceCollectionType", "traits": { - "smithy.api#documentation": "The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n 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 versions\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 path to the Amazon S3 location where logs for this cluster are stored.
" + "smithy.api#documentation": "The path to the Amazon S3 location where logs for this cluster are\n stored.
" } }, "LogEncryptionKmsKeyId": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The KMS key used for encrypting log files. This attribute is\n only available with EMR version 5.30.0 and later, excluding EMR 6.0.0.
" + "smithy.api#documentation": "The KMS key used for encrypting log files. This attribute is only\n available with EMR version 5.30.0 and later, excluding EMR 6.0.0.
" } }, "RequestedAmiVersion": { @@ -867,7 +867,7 @@ "ReleaseLabel": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The Amazon EMR release label, which determines the version of open-source application\n packages installed on the cluster. Release labels are in the form emr-x.x.x,\n where x.x.x is an Amazon EMR release version such as emr-5.14.0. For more\n information about Amazon EMR release versions and included application versions and\n features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release\n label applies only to Amazon EMR releases version 4.0 and later. Earlier versions use\n 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 later. Earlier versions use AmiVersion.
Indicates whether Amazon EMR will lock the cluster to prevent the EC2 instances from\n being terminated by an API call or user intervention, or in the event of a cluster\n error.
" + "smithy.api#documentation": "Indicates whether Amazon EMR will lock the cluster to prevent the EC2 instances\n from being terminated by an API call or user intervention, or in the event of a cluster\n error.
" } }, "VisibleToAllUsers": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "Indicates whether the cluster is visible to IAM principals in the Amazon Web Services account associated\n with the cluster. When true, IAM principals in the\n Amazon Web Services account can perform EMR cluster actions on the cluster that their IAM policies allow. When false, only the IAM principal that created the cluster and the Amazon Web Services account root user can perform EMR actions, regardless of IAM permissions policies attached to other IAM principals.
The default value is true if a value is not provided when creating a\n cluster using the EMR API RunJobFlow command, the CLI\n create-cluster command, or the Amazon Web Services Management Console.
Indicates whether the cluster is visible to IAM principals in the Amazon Web Services account associated with the cluster. When true, IAM principals\n in the Amazon Web Services account can perform EMR cluster actions on the cluster that their\n IAM policies allow. When false, only the IAM principal that created the\n cluster and the Amazon Web Services account root user can perform EMR actions, regardless of\n IAM permissions policies attached to other IAM principals.
The default value is true if a value is not provided when creating a\n cluster using the EMR API RunJobFlow command, the CLI\n create-cluster command, or the Amazon Web Services Management Console.
The IAM role that Amazon EMR assumes in order to access Amazon Web Services resources on\n your behalf.
" + "smithy.api#documentation": "The IAM role that Amazon EMR assumes in order to access Amazon Web Services\n resources on your behalf.
" } }, "NormalizedInstanceHours": { @@ -921,7 +921,7 @@ "Configurations": { "target": "com.amazonaws.emr#ConfigurationList", "traits": { - "smithy.api#documentation": "Applies only to Amazon EMR releases 4.x and later. The list of Configurations supplied\n to the EMR cluster.
" + "smithy.api#documentation": "Applies only to Amazon EMR releases 4.x and later. The list of Configurations\n supplied to the EMR cluster.
" } }, "SecurityConfiguration": { @@ -939,7 +939,7 @@ "ScaleDownBehavior": { "target": "com.amazonaws.emr#ScaleDownBehavior", "traits": { - "smithy.api#documentation": "The way that individual Amazon EC2 instances terminate when an automatic scale-in\n activity occurs or an instance group is resized. TERMINATE_AT_INSTANCE_HOUR\n indicates that Amazon EMR terminates nodes at the instance-hour boundary, regardless of\n when the request to terminate the instance was submitted. This option is only available\n with Amazon EMR 5.1.0 and later and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes to a deny\n list and drains tasks from nodes before terminating the Amazon EC2 instances, regardless of\n the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes\n first and blocks instance termination if it could lead to HDFS corruption.\n TERMINATE_AT_TASK_COMPLETION is available only in Amazon EMR version 4.1.0\n 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 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 version 4.1.0 and later, and is the default for versions of Amazon EMR earlier than 5.1.0.
The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is used for\n each EC2 instance. Available in Amazon EMR version 4.x and later.
" + "smithy.api#documentation": "The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is\n used for each EC2 instance. Available in Amazon EMR version 4.x and later.
" } }, "RepoUpgradeOnBoot": { @@ -989,6 +989,12 @@ "traits": { "smithy.api#documentation": "Placement group configured for an Amazon EMR cluster.
" } + }, + "OSReleaseLabel": { + "target": "com.amazonaws.emr#String", + "traits": { + "smithy.api#documentation": "The Amazon Linux release specified in a cluster launch RunJobFlow request. If no Amazon Linux release was specified, the default Amazon Linux release is shown in the response.
" + } } }, "traits": { @@ -1338,7 +1344,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\n configuration consists of a classification, properties, and optional nested configurations.\n A classification refers to an application-specific configuration file. Properties are the\n settings you want to change in that file. For more information, see Configuring\n Applications.
" + "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.
" } }, "com.amazonaws.emr#ConfigurationList": { @@ -1380,7 +1386,7 @@ "SecurityConfiguration": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The security configuration details in JSON format. For JSON parameters and examples, see\n Use Security\n Configurations to Set Up Cluster Security in the Amazon EMR Management\n Guide.
", + "smithy.api#documentation": "The security configuration details in JSON format. For JSON parameters and examples, see\n Use Security\n Configurations to Set Up Cluster Security in the Amazon EMR\n Management Guide.
", "smithy.api#required": {} } } @@ -1458,60 +1464,60 @@ "SubnetIds": { "target": "com.amazonaws.emr#SubnetIdList", "traits": { - "smithy.api#documentation": "A list of subnet IDs to associate with the Amazon EMR Studio. A Studio can have a maximum of 5 subnets. The subnets must belong to the VPC\n specified by VpcId. Studio users can create a Workspace in any of the\n specified subnets.
A list of subnet IDs to associate with the Amazon EMR Studio. A Studio can have\n a maximum of 5 subnets. The subnets must belong to the VPC specified by VpcId.\n Studio users can create a Workspace in any of the specified subnets.
The IAM role that the Amazon EMR Studio assumes. The service role provides a\n way for Amazon EMR Studio to interoperate with other Amazon Web Services services.
", + "smithy.api#documentation": "The IAM role that the Amazon EMR Studio assumes. The service role provides a way\n for Amazon EMR Studio to interoperate with other Amazon Web Services\n services.
", "smithy.api#required": {} } }, "UserRole": { "target": "com.amazonaws.emr#XmlString", "traits": { - "smithy.api#documentation": "The IAM user role that users and groups assume when logged in to an Amazon EMR Studio. Only specify a UserRole when you use Amazon Web Services SSO authentication. The\n permissions attached to the UserRole can be scoped down for each user or group using\n session policies.
The IAM user role that users and groups assume when logged in to an Amazon EMR\n Studio. Only specify a UserRole when you use Amazon Web Services SSO\n authentication. The permissions attached to the UserRole can be scoped down\n for each user or group using session policies.
The ID of the Amazon EMR Studio Workspace security group. The Workspace security group\n allows outbound network traffic to resources in the Engine security group, and it must be\n in the same VPC specified by VpcId.
The ID of the Amazon EMR Studio Workspace security group. The Workspace security\n group allows outbound network traffic to resources in the Engine security group, and it\n must be in the same VPC specified by VpcId.
The ID of the Amazon EMR Studio Engine security group. The Engine security group allows\n inbound network traffic from the Workspace security group, and it must be in the same VPC\n specified by VpcId.
The ID of the Amazon EMR Studio Engine security group. The Engine security group\n allows inbound network traffic from the Workspace security group, and it must be in the\n same VPC specified by VpcId.
The Amazon S3 location to back up Amazon EMR Studio Workspaces and notebook files.
", + "smithy.api#documentation": "The Amazon S3 location to back up Amazon EMR Studio Workspaces and\n notebook files.
", "smithy.api#required": {} } }, "IdpAuthUrl": { "target": "com.amazonaws.emr#XmlString", "traits": { - "smithy.api#documentation": "The authentication endpoint of your identity provider (IdP). Specify this value when you use IAM authentication and want to let federated users log in to a Studio with the Studio URL and credentials from your IdP. Amazon EMR Studio redirects users to this endpoint to enter credentials.
" + "smithy.api#documentation": "The authentication endpoint of your identity provider (IdP). Specify this value when you\n use IAM authentication and want to let federated users log in to a Studio\n with the Studio URL and credentials from your IdP. Amazon EMR Studio redirects\n users to this endpoint to enter credentials.
" } }, "IdpRelayStateParameterName": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The name that your identity provider (IdP) uses for its RelayState parameter. For example, RelayState or TargetSource. Specify this value when you use IAM authentication and want to let federated users log in to a Studio using the Studio URL. The RelayState parameter differs by IdP.
The name that your identity provider (IdP) uses for its RelayState\n parameter. For example, RelayState or TargetSource. Specify this\n value when you use IAM authentication and want to let federated users log in\n to a Studio using the Studio URL. The RelayState parameter differs by\n IdP.
A list of tags to associate with the Amazon EMR Studio. Tags are user-defined key-value pairs that\n consist of a required key string with a maximum of 128 characters, and an optional value\n string with a maximum of 256 characters.
" + "smithy.api#documentation": "A list of tags to associate with the Amazon EMR Studio. Tags are user-defined\n key-value pairs that consist of a required key string with a maximum of 128 characters, and\n an optional value string with a maximum of 256 characters.
" } } } @@ -1538,6 +1544,9 @@ "input": { "target": "com.amazonaws.emr#CreateStudioSessionMappingInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" @@ -1547,7 +1556,7 @@ } ], "traits": { - "smithy.api#documentation": "Maps a user or group to the Amazon EMR Studio specified by StudioId, and\n applies a session policy to refine Studio permissions for that user or group. Use CreateStudioSessionMapping to assign users to a Studio when you use Amazon Web Services SSO authentication. For instructions on how to assign users to a Studio when you use IAM authentication, see Assign a user or group to your EMR Studio.
Maps a user or group to the Amazon EMR Studio specified by\n StudioId, and applies a session policy to refine Studio permissions for that\n user or group. Use CreateStudioSessionMapping to assign users to a Studio when\n you use Amazon Web Services SSO authentication. For instructions on how to assign users to a\n Studio when you use IAM authentication, see Assign a user or group to your EMR Studio.
The ID of the Amazon EMR Studio to which the user or group will be mapped.
", + "smithy.api#documentation": "The ID of the Amazon EMR Studio to which the user or group will be\n mapped.
", "smithy.api#required": {} } }, "IdentityId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The globally unique identifier (GUID) of the user or group from the Amazon Web Services SSO Identity\n Store. For more information, see UserId and GroupId in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified, but not both.
The globally unique identifier (GUID) of the user or group from the Amazon Web Services SSO\n Identity Store. For more information, see UserId and GroupId in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified, but not both.
The name of the user or group. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified, but not both.
The name of the user or group. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified, but not both.
Specifies whether the identity to map to the Amazon EMR Studio is a user or a group.
", + "smithy.api#documentation": "Specifies whether the identity to map to the Amazon EMR Studio is a user or a\n group.
", "smithy.api#required": {} } }, "SessionPolicyArn": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The Amazon Resource Name (ARN) for the session policy that will be applied to the user\n or group. You should specify the ARN for the session policy that you want to apply, not the ARN of your user role. For more information, see Create an EMR Studio User Role with Session Policies.
", + "smithy.api#documentation": "The Amazon Resource Name (ARN) for the session policy that will be applied to the user\n or group. You should specify the ARN for the session policy that you want to apply, not the\n ARN of your user role. For more information, see Create an EMR Studio User\n Role with Session Policies.
", "smithy.api#required": {} } } @@ -1632,6 +1641,9 @@ "input": { "target": "com.amazonaws.emr#DeleteStudioInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerException" @@ -1661,6 +1673,9 @@ "input": { "target": "com.amazonaws.emr#DeleteStudioSessionMappingInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" @@ -1686,19 +1701,19 @@ "IdentityId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The globally unique identifier (GUID) of the user or group to remove from the Amazon EMR\n Studio. For more information, see UserId and GroupId in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified.
The globally unique identifier (GUID) of the user or group to remove from the Amazon EMR Studio. For more information, see UserId and GroupId in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified.
The name of the user name or group to remove from the Amazon EMR Studio. For more information, see\n UserName and DisplayName in the Amazon Web Services SSO Store API Reference.\n Either IdentityName or IdentityId must be specified.
The name of the user name or group to remove from the Amazon EMR Studio. For\n more information, see UserName and DisplayName in the Amazon Web Services SSO Store API Reference.\n Either IdentityName or IdentityId must be specified.
Specifies whether the identity to delete from the Amazon EMR Studio is a user or a group.
", + "smithy.api#documentation": "Specifies whether the identity to delete from the Amazon EMR Studio is a user or\n a group.
", "smithy.api#required": {} } } @@ -1959,7 +1974,7 @@ } ], "traits": { - "smithy.api#documentation": "Provides EMR release label details, such as releases available the region where the API request is run, and the available applications for a specific EMR release label. Can also list EMR release versions that support a specified version of Spark.
" + "smithy.api#documentation": "Provides EMR release label details, such as releases available the region where the API\n request is run, and the available applications for a specific EMR release label. Can also\n list EMR release versions that support a specified version of Spark.
" } }, "com.amazonaws.emr#DescribeReleaseLabelInput": { @@ -1997,7 +2012,7 @@ "Applications": { "target": "com.amazonaws.emr#SimplifiedApplicationList", "traits": { - "smithy.api#documentation": "The list of applications available for the target release label. Name is the name of the application. Version is the concise version of the application.
The list of applications available for the target release label. Name is\n the name of the application. Version is the concise version of the\n application.
The pagination token. Reserved for future use. Currently set to null.
" } + }, + "AvailableOSReleases": { + "target": "com.amazonaws.emr#OSReleaseList", + "traits": { + "smithy.api#documentation": "The list of available Amazon Linux release versions for an Amazon EMR release. \n Contains a Label field that is formatted as shown in \n Amazon Linux 2 Release Notes\n . For example, 2.0.20220218.1.
" + } } } }, @@ -2173,7 +2194,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns details for the specified Amazon EMR Studio including ID, Name, VPC, Studio\n access URL, and so on.
" + "smithy.api#documentation": "Returns details for the specified Amazon EMR Studio including ID, Name, VPC,\n Studio access URL, and so on.
" } }, "com.amazonaws.emr#DescribeStudioInput": { @@ -2270,7 +2291,7 @@ "EbsBlockDeviceConfigs": { "target": "com.amazonaws.emr#EbsBlockDeviceConfigList", "traits": { - "smithy.api#documentation": "An array of Amazon EBS volume specifications attached to a cluster instance.
" + "smithy.api#documentation": "An array of Amazon EBS volume specifications attached to a cluster\n instance.
" } }, "EbsOptimized": { @@ -2316,19 +2337,19 @@ "Ec2KeyName": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The name of the Amazon EC2 key pair to use when connecting with SSH into the master node\n as a user named \"hadoop\".
" + "smithy.api#documentation": "The name of the Amazon EC2 key pair to use when connecting with SSH into the\n master node as a user named \"hadoop\".
" } }, "Ec2SubnetId": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "Set this parameter to the identifier of the Amazon VPC subnet where you want the cluster\n to launch. If you do not specify this value, and your account supports EC2-Classic, the\n cluster launches in EC2-Classic.
" + "smithy.api#documentation": "Set this parameter to the identifier of the Amazon VPC subnet where you want the\n cluster to launch. If you do not specify this value, and your account supports EC2-Classic,\n the cluster launches in EC2-Classic.
" } }, "RequestedEc2SubnetIds": { "target": "com.amazonaws.emr#XmlStringMaxLen256List", "traits": { - "smithy.api#documentation": "Applies to clusters configured with the instance fleets option. Specifies the unique\n identifier of one or more Amazon EC2 subnets in which to launch EC2 cluster instances.\n Subnets must exist within the same VPC. Amazon EMR chooses the EC2 subnet with the best fit\n from among the list of RequestedEc2SubnetIds, and then launches all cluster\n instances within that Subnet. If this value is not specified, and the account and Region\n support EC2-Classic networks, the cluster launches instances in the EC2-Classic network and\n uses RequestedEc2AvailabilityZones instead of this setting. If EC2-Classic is\n not supported, and no Subnet is specified, Amazon EMR chooses the subnet for you.\n RequestedEc2SubnetIDs and RequestedEc2AvailabilityZones cannot\n be specified together.
Applies to clusters configured with the instance fleets option. Specifies the unique\n identifier of one or more Amazon EC2 subnets in which to launch EC2 cluster\n instances. Subnets must exist within the same VPC. Amazon EMR chooses the EC2\n subnet with the best fit from among the list of RequestedEc2SubnetIds, and\n then launches all cluster instances within that Subnet. If this value is not specified, and\n the account and Region support EC2-Classic networks, the cluster launches instances in the\n EC2-Classic network and uses RequestedEc2AvailabilityZones instead of this\n setting. If EC2-Classic is not supported, and no Subnet is specified, Amazon EMR\n chooses the subnet for you. RequestedEc2SubnetIDs and\n RequestedEc2AvailabilityZones cannot be specified together.
Applies to clusters configured with the instance fleets option. Specifies one or more\n Availability Zones in which to launch EC2 cluster instances when the EC2-Classic network\n configuration is supported. Amazon EMR chooses the Availability Zone with the best fit from\n among the list of RequestedEc2AvailabilityZones, and then launches all cluster\n instances within that Availability Zone. If you do not specify this value, Amazon EMR\n chooses the Availability Zone for you. RequestedEc2SubnetIDs and\n RequestedEc2AvailabilityZones cannot be specified together.
Applies to clusters configured with the instance fleets option. Specifies one or more\n Availability Zones in which to launch EC2 cluster instances when the EC2-Classic network\n configuration is supported. Amazon EMR chooses the Availability Zone with the best\n fit from among the list of RequestedEc2AvailabilityZones, and then launches\n all cluster instances within that Availability Zone. If you do not specify this value,\n Amazon EMR chooses the Availability Zone for you.\n RequestedEc2SubnetIDs and RequestedEc2AvailabilityZones cannot\n be specified together.
The identifier of the Amazon EC2 security group for the core and task nodes.
" + "smithy.api#documentation": "The identifier of the Amazon EC2 security group for the core and task\n nodes.
" } }, "ServiceAccessSecurityGroup": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The identifier of the Amazon EC2 security group for the Amazon EMR service to access\n clusters in VPC private subnets.
" + "smithy.api#documentation": "The identifier of the Amazon EC2 security group for the Amazon EMR\n service to access clusters in VPC private subnets.
" } }, "AdditionalMasterSecurityGroups": { @@ -2376,7 +2397,7 @@ "AdditionalSlaveSecurityGroups": { "target": "com.amazonaws.emr#StringList", "traits": { - "smithy.api#documentation": "A list of additional Amazon EC2 security group IDs for the core and task nodes.
" + "smithy.api#documentation": "A list of additional Amazon EC2 security group IDs for the core and task\n nodes.
" } } }, @@ -2398,7 +2419,7 @@ "name": "elasticmapreduce" }, "aws.protocols#awsJson1_1": {}, - "smithy.api#documentation": "Amazon EMR is a web service that makes it easier to process large amounts of data\n efficiently. Amazon EMR uses Hadoop processing combined with several Amazon Web Services services to do\n tasks such as web indexing, data mining, log file analysis, machine learning, scientific\n simulation, and data warehouse management.
", + "smithy.api#documentation": "Amazon EMR is a web service that makes it easier to process large amounts of\n data efficiently. Amazon EMR uses Hadoop processing combined with several Amazon Web Services services to do tasks such as web indexing, data mining, log file analysis,\n machine learning, scientific simulation, and data warehouse management.
", "smithy.api#title": "Amazon EMR", "smithy.api#xmlNamespace": { "uri": "http://elasticmapreduce.amazonaws.com/doc/2009-03-31" @@ -2626,7 +2647,7 @@ "Message": { "target": "com.amazonaws.emr#String", "traits": { - "smithy.api#documentation": "The descriptive message including the error the Amazon EMR service has identified as the\n cause of step failure. This is text from an error log that describes the root cause of the\n failure.
" + "smithy.api#documentation": "The descriptive message including the error the Amazon EMR service has\n identified as the cause of step failure. This is text from an error log that describes the\n root cause of the failure.
" } }, "LogFile": { @@ -2658,7 +2679,7 @@ "ClusterId": { "target": "com.amazonaws.emr#ClusterId", "traits": { - "smithy.api#documentation": "Specifies the ID of the Amazon EMR cluster for which the auto-termination policy will be fetched.
", + "smithy.api#documentation": "Specifies the ID of the Amazon EMR cluster for which the auto-termination policy\n will be fetched.
", "smithy.api#required": {} } } @@ -2670,7 +2691,7 @@ "AutoTerminationPolicy": { "target": "com.amazonaws.emr#AutoTerminationPolicy", "traits": { - "smithy.api#documentation": "Specifies the auto-termination policy that is attached to an Amazon EMR cluster.
" + "smithy.api#documentation": "Specifies the auto-termination policy that is attached to an Amazon EMR cluster.\n
" } } } @@ -2692,7 +2713,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns the Amazon EMR block public access configuration for your Amazon Web Services account in the\n current Region. For more information see Configure Block\n Public Access for Amazon EMR in the Amazon EMR Management\n Guide.
" + "smithy.api#documentation": "Returns the Amazon EMR block public access configuration for your Amazon Web Services account in the current Region. For more information see Configure Block\n Public Access for Amazon EMR in the Amazon EMR\n Management Guide.
" } }, "com.amazonaws.emr#GetBlockPublicAccessConfigurationInput": { @@ -2705,7 +2726,7 @@ "BlockPublicAccessConfiguration": { "target": "com.amazonaws.emr#BlockPublicAccessConfiguration", "traits": { - "smithy.api#documentation": "A configuration for Amazon EMR block public access. The configuration applies to all\n 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 EMR cluster in a Region\n before this date, block public access is enabled by default in that 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. 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 EMR cluster in a Region\n before this date, block public access is enabled by default in that Region.
\nSpecifies the managed scaling policy that is attached to an Amazon EMR cluster.
" + "smithy.api#documentation": "Specifies the managed scaling policy that is attached to an Amazon EMR cluster.\n
" } } } @@ -2770,7 +2791,7 @@ } ], "traits": { - "smithy.api#documentation": "Fetches mapping details for the specified Amazon EMR Studio and identity (user or\n group).
" + "smithy.api#documentation": "Fetches mapping details for the specified Amazon EMR Studio and identity (user\n or group).
" } }, "com.amazonaws.emr#GetStudioSessionMappingInput": { @@ -2786,13 +2807,13 @@ "IdentityId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The globally unique identifier (GUID) of the user or group. For more information, see\n UserId and GroupId in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified.
The globally unique identifier (GUID) of the user or group. For more information, see\n UserId and GroupId in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified.
The name of the user or group to fetch. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified.
The name of the user or group to fetch. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified.
The session mapping details for the specified Amazon EMR Studio and identity, including\n session policy ARN and creation time.
" + "smithy.api#documentation": "The session mapping details for the specified Amazon EMR Studio and identity,\n including session policy ARN and creation time.
" } } } @@ -3020,13 +3041,13 @@ "TargetOnDemandCapacity": { "target": "com.amazonaws.emr#WholeNumber", "traits": { - "smithy.api#documentation": "The target capacity of On-Demand units for the instance fleet, which determines how many\n On-Demand Instances to provision. When the instance fleet launches, Amazon EMR tries to\n provision On-Demand Instances as specified by InstanceTypeConfig. Each\n instance configuration has a specified WeightedCapacity. When an On-Demand\n Instance is provisioned, the WeightedCapacity units count toward the target\n capacity. Amazon EMR provisions instances until the target capacity is totally fulfilled,\n even if this results in an overage. For example, if there are 2 units remaining to fulfill\n capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units. You can use InstanceFleet$ProvisionedOnDemandCapacity to determine the Spot capacity\n units that have been provisioned for the instance fleet.
If not specified or set to 0, only Spot Instances are provisioned for the instance\n fleet using TargetSpotCapacity. At least one of\n TargetSpotCapacity and TargetOnDemandCapacity should be\n greater than 0. For a master instance fleet, only one of TargetSpotCapacity\n and TargetOnDemandCapacity can be specified, and its value must be\n 1.
The target capacity of On-Demand units for the instance fleet, which determines how many\n On-Demand Instances to provision. When the instance fleet launches, Amazon EMR\n tries to provision On-Demand Instances as specified by InstanceTypeConfig. Each instance configuration has a specified WeightedCapacity. When an\n On-Demand Instance is provisioned, the WeightedCapacity units count toward the\n target capacity. Amazon EMR provisions instances until the target capacity is\n totally fulfilled, even if this results in an overage. For example, if there are 2 units\n remaining to fulfill capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units. You can use InstanceFleet$ProvisionedOnDemandCapacity to determine the Spot capacity\n units that have been provisioned for the instance fleet.
If not specified or set to 0, only Spot Instances are provisioned for the instance\n fleet using TargetSpotCapacity. At least one of\n TargetSpotCapacity and TargetOnDemandCapacity should be\n greater than 0. For a master instance fleet, only one of TargetSpotCapacity\n and TargetOnDemandCapacity can be specified, and its value must be\n 1.
The target capacity of Spot units for the instance fleet, which determines how many Spot\n Instances to provision. When the instance fleet launches, Amazon EMR tries to provision\n Spot Instances as specified by InstanceTypeConfig. Each instance\n configuration has a specified WeightedCapacity. When a Spot instance is\n provisioned, the WeightedCapacity units count toward the target capacity.\n Amazon EMR provisions instances until the target capacity is totally fulfilled, even if\n this results in an overage. For example, if there are 2 units remaining to fulfill\n capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units. You can use InstanceFleet$ProvisionedSpotCapacity to determine the Spot capacity units\n that have been provisioned for the instance fleet.
If not specified or set to 0, only On-Demand Instances are provisioned for the\n instance fleet. At least one of TargetSpotCapacity and\n TargetOnDemandCapacity should be greater than 0. For a master instance\n fleet, only one of TargetSpotCapacity and\n TargetOnDemandCapacity can be specified, and its value must be 1.
The target capacity of Spot units for the instance fleet, which determines how many Spot\n Instances to provision. When the instance fleet launches, Amazon EMR tries to\n provision Spot Instances as specified by InstanceTypeConfig. Each\n instance configuration has a specified WeightedCapacity. When a Spot instance\n is provisioned, the WeightedCapacity units count toward the target capacity.\n Amazon EMR provisions instances until the target capacity is totally fulfilled,\n even if this results in an overage. For example, if there are 2 units remaining to fulfill\n capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units. You can use InstanceFleet$ProvisionedSpotCapacity to determine the Spot capacity units\n that have been provisioned for the instance fleet.
If not specified or set to 0, only On-Demand Instances are provisioned for the\n instance fleet. At least one of TargetSpotCapacity and\n TargetOnDemandCapacity should be greater than 0. For a master instance\n fleet, only one of TargetSpotCapacity and\n TargetOnDemandCapacity can be specified, and its value must be 1.
An array of specifications for the instance types that comprise an instance fleet.
" + "smithy.api#documentation": "An array of specifications for the instance types that comprise an instance\n fleet.
" } }, "LaunchSpecifications": { @@ -3055,7 +3076,7 @@ } }, "traits": { - "smithy.api#documentation": "Describes an instance fleet, which is a group of EC2 instances that host a particular\n node type (master, core, or task) in an Amazon EMR cluster. Instance fleets can consist of\n a mix of instance types and On-Demand and Spot Instances, which are provisioned to meet a\n defined target capacity.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x versions.
\nDescribes an instance fleet, which is a group of EC2 instances that host a particular\n node type (master, core, or task) in an Amazon EMR cluster. Instance fleets can\n consist of a mix of instance types and On-Demand and Spot Instances, which are provisioned\n to meet a defined target capacity.
\nThe instance fleet configuration is available only in Amazon EMR versions\n 4.8.0 and later, excluding 5.0.x versions.
\nThe target capacity of On-Demand units for the instance fleet, which determines how many\n On-Demand Instances to provision. When the instance fleet launches, Amazon EMR tries to\n provision On-Demand Instances as specified by InstanceTypeConfig. Each\n instance configuration has a specified WeightedCapacity. When an On-Demand\n Instance is provisioned, the WeightedCapacity units count toward the target\n capacity. Amazon EMR provisions instances until the target capacity is totally fulfilled,\n even if this results in an overage. For example, if there are 2 units remaining to fulfill\n capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units.
If not specified or set to 0, only Spot Instances are provisioned for the instance\n fleet using TargetSpotCapacity. At least one of\n TargetSpotCapacity and TargetOnDemandCapacity should be\n greater than 0. For a master instance fleet, only one of TargetSpotCapacity\n and TargetOnDemandCapacity can be specified, and its value must be\n 1.
The target capacity of On-Demand units for the instance fleet, which determines how many\n On-Demand Instances to provision. When the instance fleet launches, Amazon EMR\n tries to provision On-Demand Instances as specified by InstanceTypeConfig. Each instance configuration has a specified WeightedCapacity. When an\n On-Demand Instance is provisioned, the WeightedCapacity units count toward the\n target capacity. Amazon EMR provisions instances until the target capacity is\n totally fulfilled, even if this results in an overage. For example, if there are 2 units\n remaining to fulfill capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units.
If not specified or set to 0, only Spot Instances are provisioned for the instance\n fleet using TargetSpotCapacity. At least one of\n TargetSpotCapacity and TargetOnDemandCapacity should be\n greater than 0. For a master instance fleet, only one of TargetSpotCapacity\n and TargetOnDemandCapacity can be specified, and its value must be\n 1.
The target capacity of Spot units for the instance fleet, which determines how many Spot\n Instances to provision. When the instance fleet launches, Amazon EMR tries to provision\n Spot Instances as specified by InstanceTypeConfig. Each instance\n configuration has a specified WeightedCapacity. When a Spot Instance is\n provisioned, the WeightedCapacity units count toward the target capacity.\n Amazon EMR provisions instances until the target capacity is totally fulfilled, even if\n this results in an overage. For example, if there are 2 units remaining to fulfill\n capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units.
If not specified or set to 0, only On-Demand Instances are provisioned for the\n instance fleet. At least one of TargetSpotCapacity and\n TargetOnDemandCapacity should be greater than 0. For a master instance\n fleet, only one of TargetSpotCapacity and\n TargetOnDemandCapacity can be specified, and its value must be 1.
The target capacity of Spot units for the instance fleet, which determines how many Spot\n Instances to provision. When the instance fleet launches, Amazon EMR tries to\n provision Spot Instances as specified by InstanceTypeConfig. Each\n instance configuration has a specified WeightedCapacity. When a Spot Instance\n is provisioned, the WeightedCapacity units count toward the target capacity.\n Amazon EMR provisions instances until the target capacity is totally fulfilled,\n even if this results in an overage. For example, if there are 2 units remaining to fulfill\n capacity, and Amazon EMR can only provision an instance with a\n WeightedCapacity of 5 units, the instance is provisioned, and the target\n capacity is exceeded by 3 units.
If not specified or set to 0, only On-Demand Instances are provisioned for the\n instance fleet. At least one of TargetSpotCapacity and\n TargetOnDemandCapacity should be greater than 0. For a master instance\n fleet, only one of TargetSpotCapacity and\n TargetOnDemandCapacity can be specified, and its value must be 1.
The configuration that defines an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x versions.
\nThe configuration that defines an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR versions\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 versions 4.8.0 and\n later, excluding 5.0.x versions.
\nConfiguration parameters for an instance fleet modification request.
\nThe instance fleet configuration is available only in Amazon EMR versions\n 4.8.0 and later, 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 versions 4.8.0 and\n later, excluding 5.0.x versions. On-Demand Instances allocation strategy is available in\n Amazon EMR version 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 versions\n 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is\n available in Amazon EMR version 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 versions 4.8.0 and\n later, excluding 5.0.x versions. On-Demand and Spot Instance allocation strategies are\n available in Amazon EMR version 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 versions\n 4.8.0 and later, excluding 5.0.x versions. On-Demand and Spot Instance allocation\n strategies are available in Amazon EMR version 5.12.1 and later.
\nProvides status change reason details for the instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n 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 versions\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 versions 4.8.0 and\n later, excluding 5.0.x versions.
\nThe status of the instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR versions\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 versions 4.8.0 and\n 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 versions\n 4.8.0 and later, excluding 5.0.x versions.
\nIf specified, indicates that the instance group uses Spot Instances. This is the maximum price you are willing to pay for Spot Instances. Specify OnDemandPrice to set the amount equal to the On-Demand price, or specify an amount in USD.
If specified, indicates that the instance group uses Spot Instances. This is the maximum\n price you are willing to pay for Spot Instances. Specify OnDemandPrice to set\n the amount equal to the On-Demand price, or specify an amount in USD.
Amazon EMR releases 4.x or later.
\nThe list of configurations supplied for an Amazon EMR cluster instance group. You can specify a\n separate configuration for each instance group (master, core, and task).
" + "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).
" } }, "ConfigurationsVersion": { @@ -3404,7 +3425,7 @@ "EbsOptimized": { "target": "com.amazonaws.emr#BooleanObject", "traits": { - "smithy.api#documentation": "If the instance group is EBS-optimized. An Amazon EBS-optimized instance uses an\n optimized configuration stack and provides additional, dedicated capacity for Amazon EBS\n I/O.
" + "smithy.api#documentation": "If the instance group is EBS-optimized. An Amazon EBS-optimized instance uses an\n optimized configuration stack and provides additional, dedicated capacity for Amazon EBS I/O.
" } }, "ShrinkPolicy": { @@ -3416,7 +3437,7 @@ "AutoScalingPolicy": { "target": "com.amazonaws.emr#AutoScalingPolicyDescription", "traits": { - "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. The automatic scaling policy defines how an instance group dynamically\n adds and terminates EC2 instances in response to the value of a CloudWatch metric. See\n PutAutoScalingPolicy.
" + "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. The automatic scaling policy defines how an instance group\n dynamically adds and terminates EC2 instances in response to the value of a CloudWatch\n metric. See PutAutoScalingPolicy.
" } }, "CustomAmiId": { @@ -3455,7 +3476,7 @@ "BidPrice": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "If specified, indicates that the instance group uses Spot Instances. This is the maximum price you are willing to pay for Spot Instances. Specify OnDemandPrice to set the amount equal to the On-Demand price, or specify an amount in USD.
If specified, indicates that the instance group uses Spot Instances. This is the maximum\n price you are willing to pay for Spot Instances. Specify OnDemandPrice to set\n the amount equal to the On-Demand price, or specify an amount in USD.
An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. The automatic scaling policy defines how an instance group dynamically\n adds and terminates EC2 instances in response to the value of a CloudWatch metric. See\n PutAutoScalingPolicy.
" + "smithy.api#documentation": "An automatic scaling policy for a core instance group or task instance group in an\n Amazon EMR cluster. The automatic scaling policy defines how an instance group\n dynamically adds and terminates EC2 instances in response to the value of a CloudWatch\n metric. See PutAutoScalingPolicy.
" } }, "CustomAmiId": { @@ -3539,7 +3560,7 @@ "BidPrice": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "If specified, indicates that the instance group uses Spot Instances. This is the maximum price you are willing to pay for Spot Instances. Specify OnDemandPrice to set the amount equal to the On-Demand price, or specify an amount in USD.
If specified, indicates that the instance group uses Spot Instances. This is the maximum\n price you are willing to pay for Spot Instances. Specify OnDemandPrice to set\n the amount equal to the On-Demand price, or specify an amount in USD.
State of instance group. The following values are no longer supported: STARTING, TERMINATED, and\n FAILED.
", + "smithy.api#documentation": "State of instance group. The following values are no longer supported: STARTING,\n TERMINATED, and FAILED.
", "smithy.api#required": {} } }, @@ -3661,6 +3682,12 @@ "smithy.api#documentation": "Policy for customizing shrink operations.
" } }, + "ReconfigurationType": { + "target": "com.amazonaws.emr#ReconfigurationType", + "traits": { + "smithy.api#documentation": "Type of reconfiguration requested. Valid values are MERGE and OVERWRITE.
" + } + }, "Configurations": { "target": "com.amazonaws.emr#ConfigurationList", "traits": { @@ -4076,7 +4103,7 @@ "EbsConfiguration": { "target": "com.amazonaws.emr#EbsConfiguration", "traits": { - "smithy.api#documentation": "The configuration of Amazon Elastic Block Store (Amazon EBS) attached to each instance\n as defined by InstanceType.
The configuration of Amazon Elastic Block Store (Amazon EBS) attached to each\n instance as defined by InstanceType.
An instance type configuration for each instance type in an instance fleet, which\n determines the EC2 instances Amazon EMR attempts to provision to fulfill On-Demand and Spot\n target capacities. When you use an allocation strategy, you can include a maximum of 30 instance type configurations for a fleet. For more information about how to use an allocation strategy, see Configure Instance Fleets. Without an allocation strategy, you may specify a maximum of five instance type configurations for a fleet.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x versions.
\nAn instance type configuration for each instance type in an instance fleet, which\n determines the EC2 instances Amazon EMR attempts to provision to fulfill On-Demand\n and Spot target capacities. When you use an allocation strategy, you can include a maximum\n of 30 instance type configurations for a fleet. For more information about how to use an\n 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 versions\n 4.8.0 and later, excluding 5.0.x versions.
\nThe configuration of Amazon Elastic Block Store (Amazon EBS) attached to each instance\n as defined by InstanceType.
The configuration of Amazon Elastic Block Store (Amazon EBS) attached to each\n instance as defined by InstanceType.
The configuration specification for each instance type in an instance fleet.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n 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 versions\n 4.8.0 and later, excluding 5.0.x versions.
\nThe KMS key used for encrypting log files. This attribute is\n only available with EMR version 5.30.0 and later, excluding EMR 6.0.0.
" + "smithy.api#documentation": "The KMS key used for encrypting log files. This attribute is only\n available with EMR version 5.30.0 and later, excluding EMR 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 releases 4.0 and\n 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 later, ReleaseLabel is used. To specify a custom AMI, use\n CustomAmiID.
Indicates whether the cluster is visible to IAM principals in the Amazon Web Services account associated\n with the cluster. When true, IAM principals in the\n Amazon Web Services account can perform EMR cluster actions that their IAM policies allow. When false, only the IAM principal that created the cluster and the Amazon Web Services account root user can perform EMR actions, regardless of IAM permissions policies attached to other IAM principals.
The default value is true if a value is not provided when creating a\n cluster using the EMR API RunJobFlow command, the CLI\n create-cluster command, or the Amazon Web Services Management Console.
Indicates whether the cluster is visible to IAM principals in the Amazon Web Services account associated with the cluster. When true, IAM principals\n in the Amazon Web Services account can perform EMR cluster actions that their IAM policies\n allow. When false, only the IAM principal that created the cluster and the\n Amazon Web Services account root user can perform EMR actions, regardless of IAM\n permissions policies attached to other IAM principals.
The default value is true if a value is not provided when creating a\n cluster using the EMR API RunJobFlow command, the CLI\n create-cluster command, or the Amazon Web Services Management Console.
The IAM role that is assumed by the Amazon EMR service to access Amazon Web Services resources on your\n behalf.
" + "smithy.api#documentation": "The IAM role that is assumed by the Amazon EMR service to access Amazon Web Services resources on your behalf.
" } }, "AutoScalingRole": { @@ -4313,7 +4340,7 @@ "ScaleDownBehavior": { "target": "com.amazonaws.emr#ScaleDownBehavior", "traits": { - "smithy.api#documentation": "The way that individual Amazon EC2 instances terminate when an automatic scale-in\n activity occurs or an instance group is resized. TERMINATE_AT_INSTANCE_HOUR\n indicates that Amazon EMR terminates nodes at the instance-hour boundary, regardless of\n when the request to terminate the instance was submitted. This option is only available\n with Amazon EMR 5.1.0 and later and is the default for clusters created using that version.\n TERMINATE_AT_TASK_COMPLETION indicates that Amazon EMR adds nodes to a deny\n list and drains tasks from nodes before terminating the Amazon EC2 instances, regardless of\n the instance-hour boundary. With either behavior, Amazon EMR removes the least active nodes\n first and blocks instance termination if it could lead to HDFS corruption.\n TERMINATE_AT_TASK_COMPLETION available only in Amazon EMR version 4.1.0 and\n 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 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 version 4.1.0 and later, and is the default for versions of Amazon EMR earlier than 5.1.0.
The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x versions.
\nDescribes the EC2 instances and instance configurations for clusters that use the\n instance fleet configuration.
" + "smithy.api#documentation": "The instance fleet configuration is available only in Amazon EMR versions\n 4.8.0 and later, excluding 5.0.x versions.
\nDescribes the EC2 instances and instance configurations for clusters that use the\n instance fleet configuration.
" } }, "Ec2KeyName": { @@ -4467,49 +4494,49 @@ "KeepJobFlowAliveWhenNoSteps": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "Specifies whether the cluster should remain available after completing all steps. Defaults to true. For more information about configuring cluster termination, see Control Cluster Termination in the EMR Management Guide.
Specifies whether the cluster should remain available after completing all steps.\n Defaults to true. For more information about configuring cluster termination,\n see Control Cluster Termination in the EMR Management\n Guide.
Specifies whether to lock the cluster to prevent the Amazon EC2 instances from being\n terminated by API call, user intervention, or in the event of a job-flow error.
" + "smithy.api#documentation": "Specifies whether to lock the cluster to prevent the Amazon EC2 instances from\n being terminated by API call, user intervention, or in the event of a job-flow\n error.
" } }, "HadoopVersion": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "Applies only to Amazon EMR release versions earlier than 4.0. The Hadoop version for the\n cluster. Valid inputs are \"0.18\" (no longer maintained), \"0.20\" (no longer maintained),\n \"0.20.205\" (no longer maintained), \"1.0.3\", \"2.2.0\", or \"2.4.0\". If you do not set this\n value, the default of 0.18 is used, unless the AmiVersion parameter is set in\n the RunJobFlow call, in which case the default version of Hadoop for that AMI version is\n used.
Applies only to Amazon EMR release versions earlier than 4.0. The Hadoop version\n for the cluster. Valid inputs are \"0.18\" (no longer maintained), \"0.20\" (no longer\n maintained), \"0.20.205\" (no longer maintained), \"1.0.3\", \"2.2.0\", or \"2.4.0\". If you do not\n set this value, the default of 0.18 is used, unless the AmiVersion parameter\n is set in the RunJobFlow call, in which case the default version of Hadoop for that AMI\n version is used.
Applies to clusters that use the uniform instance group configuration. To launch the\n cluster in Amazon Virtual Private Cloud (Amazon VPC), set this parameter to the identifier\n of the Amazon VPC subnet where you want the cluster to launch. If you do not specify this\n value and your account supports EC2-Classic, the cluster launches in EC2-Classic.
" + "smithy.api#documentation": "Applies to clusters that use the uniform instance group configuration. To launch the\n cluster in Amazon Virtual Private Cloud (Amazon VPC), set this parameter to the\n identifier of the Amazon VPC subnet where you want the cluster to launch. If you do\n not specify this value and your account supports EC2-Classic, the cluster launches in\n EC2-Classic.
" } }, "Ec2SubnetIds": { "target": "com.amazonaws.emr#XmlStringMaxLen256List", "traits": { - "smithy.api#documentation": "Applies to clusters that use the instance fleet configuration. When multiple EC2 subnet\n IDs are specified, Amazon EMR evaluates them and launches instances in the optimal\n subnet.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x versions.
\nApplies to clusters that use the instance fleet configuration. When multiple EC2 subnet\n IDs are specified, Amazon EMR evaluates them and launches instances in the optimal\n subnet.
\nThe instance fleet configuration is available only in Amazon EMR versions\n 4.8.0 and later, excluding 5.0.x versions.
\nThe identifier of the Amazon EC2 security group for the master node. If you specify EmrManagedMasterSecurityGroup, you must also specify EmrManagedSlaveSecurityGroup.
The identifier of the Amazon EC2 security group for the master node. If you\n specify EmrManagedMasterSecurityGroup, you must also specify\n EmrManagedSlaveSecurityGroup.
The identifier of the Amazon EC2 security group for the core and task nodes. If you specify EmrManagedSlaveSecurityGroup, you must also specify EmrManagedMasterSecurityGroup.
The identifier of the Amazon EC2 security group for the core and task nodes. If\n you specify EmrManagedSlaveSecurityGroup, you must also specify\n EmrManagedMasterSecurityGroup.
The identifier of the Amazon EC2 security group for the Amazon EMR service to access\n clusters in VPC private subnets.
" + "smithy.api#documentation": "The identifier of the Amazon EC2 security group for the Amazon EMR\n service to access clusters in VPC private subnets.
" } }, "AdditionalMasterSecurityGroups": { @@ -4521,12 +4548,12 @@ "AdditionalSlaveSecurityGroups": { "target": "com.amazonaws.emr#SecurityGroupsList", "traits": { - "smithy.api#documentation": "A list of additional Amazon EC2 security group IDs for the core and task nodes.
" + "smithy.api#documentation": "A list of additional Amazon EC2 security group IDs for the core and task\n nodes.
" } } }, "traits": { - "smithy.api#documentation": "A description of the Amazon EC2 instance on which the cluster (job flow) runs. A valid\n JobFlowInstancesConfig must contain either InstanceGroups or InstanceFleets. They cannot be\n used together. You may also have MasterInstanceType, SlaveInstanceType, and InstanceCount\n (all three must be present), but we don't recommend this configuration.
" + "smithy.api#documentation": "A description of the Amazon EC2 instance on which the cluster (job flow) runs. A\n valid JobFlowInstancesConfig must contain either InstanceGroups or InstanceFleets. They\n cannot be used together. You may also have MasterInstanceType, SlaveInstanceType, and\n InstanceCount (all three must be present), but we don't recommend this\n configuration.
" } }, "com.amazonaws.emr#JobFlowInstancesDetail": { @@ -4561,7 +4588,7 @@ "InstanceCount": { "target": "com.amazonaws.emr#Integer", "traits": { - "smithy.api#documentation": "The number of Amazon EC2 instances in the cluster. If the value is 1, the same instance\n serves as both the master and core and task node. If the value is greater than 1, one\n instance is the master node and all others are core and task nodes.
", + "smithy.api#documentation": "The number of Amazon EC2 instances in the cluster. If the value is 1, the same\n instance serves as both the master and core and task node. If the value is greater than 1,\n one instance is the master node and all others are core and task nodes.
", "smithy.api#required": {} } }, @@ -4574,13 +4601,13 @@ "NormalizedInstanceHours": { "target": "com.amazonaws.emr#Integer", "traits": { - "smithy.api#documentation": "An approximation of the cost of the cluster, represented in m1.small/hours. This value\n is increased one time for every hour that an m1.small instance runs. Larger instances are\n weighted more heavily, so an Amazon EC2 instance that is roughly four times more expensive\n would result in the normalized instance hours being increased incrementally four times.\n This result is only an approximation and does not reflect the actual billing rate.
" + "smithy.api#documentation": "An approximation of the cost of the cluster, represented in m1.small/hours. This value\n is increased one time for every hour that an m1.small instance runs. Larger instances are\n weighted more heavily, so an Amazon EC2 instance that is roughly four times more\n expensive would result in the normalized instance hours being increased incrementally four\n times. This result is only an approximation and does not reflect the actual billing\n rate.
" } }, "Ec2KeyName": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The name of an Amazon EC2 key pair that can be used to connect to the master node using\n SSH.
" + "smithy.api#documentation": "The name of an Amazon EC2 key pair that can be used to connect to the master\n node using SSH.
" } }, "Ec2SubnetId": { @@ -4604,7 +4631,7 @@ "TerminationProtected": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "Specifies whether the Amazon EC2 instances in the cluster are protected from termination\n by API calls, user intervention, or in the event of a job-flow error.
" + "smithy.api#documentation": "Specifies whether the Amazon EC2 instances in the cluster are protected from\n termination by API calls, user intervention, or in the event of a job-flow error.
" } }, "HadoopVersion": { @@ -4615,7 +4642,7 @@ } }, "traits": { - "smithy.api#documentation": "Specify the type of Amazon EC2 instances that the cluster (job flow) runs on.
" + "smithy.api#documentation": "Specify the type of Amazon EC2 instances that the cluster (job flow) runs\n on.
" } }, "com.amazonaws.emr#KerberosAttributes": { @@ -4767,7 +4794,7 @@ } ], "traits": { - "smithy.api#documentation": "Provides the status of all clusters visible to this Amazon Web Services account. Allows you to filter\n the list of clusters based on certain criteria; for example, filtering by cluster creation\n date and time or by status. This call returns a maximum of 50 clusters in unsorted order per call, but\n returns a marker to track the paging of the cluster list across multiple ListClusters\n calls.
", + "smithy.api#documentation": "Provides the status of all clusters visible to this Amazon Web Services account. Allows\n you to filter the list of clusters based on certain criteria; for example, filtering by\n cluster creation date and time or by status. This call returns a maximum of 50 clusters in\n unsorted order per call, but returns a marker to track the paging of the cluster list\n across multiple ListClusters calls.
", "smithy.api#paginated": { "inputToken": "Marker", "outputToken": "Marker", @@ -4793,7 +4820,7 @@ "ClusterStates": { "target": "com.amazonaws.emr#ClusterStateList", "traits": { - "smithy.api#documentation": "The cluster state filters to apply when listing clusters. Clusters that change state while this action runs may be not be returned as expected in the list of clusters.
" + "smithy.api#documentation": "The cluster state filters to apply when listing clusters. Clusters that change state\n while this action runs may be not be returned as expected in the list of clusters.
" } }, "Marker": { @@ -4844,7 +4871,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists all available details about the instance fleets in a cluster.
\nThe instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n 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 versions\n 4.8.0 and later, excluding 5.0.x versions.
\nFilters the results of the request. Prefix specifies the prefix of release labels to return. Application specifies the application (with/without version) of release labels to return.
Filters the results of the request. Prefix specifies the prefix of release\n labels to return. Application specifies the application (with/without version)\n of release labels to return.
Specifies the next page of results. If NextToken is not specified, which is usually the case for the first request of ListReleaseLabels, the first page of results are determined by other filtering parameters or by the latest version. The ListReleaseLabels request fails if the identity (Amazon Web Services account ID) and all filtering parameters are different from the original request, or if the NextToken is expired or tampered with.
Specifies the next page of results. If NextToken is not specified, which is\n usually the case for the first request of ListReleaseLabels, the first page of results are\n determined by other filtering parameters or by the latest version. The\n ListReleaseLabels request fails if the identity (Amazon Web Services account\n ID) and all filtering parameters are different from the original request, or if the\n NextToken is expired or tampered with.
Defines the maximum number of release labels to return in a single response. The default is 100.
Defines the maximum number of release labels to return in a single response. The default\n is 100.
Used to paginate the next page of results if specified in the next ListReleaseLabels request.
Used to paginate the next page of results if specified in the next\n ListReleaseLabels request.
Provides a list of steps for the cluster in reverse order unless you specify\n stepIds with the request or filter by StepStates. You can\n specify a maximum of 10 stepIDs. The CLI automatically paginates results to return a list greater than 50 steps. To return more than 50 steps using the CLI, specify a Marker, which is a pagination token that indicates the next set of steps to retrieve.
Provides a list of steps for the cluster in reverse order unless you specify\n stepIds with the request or filter by StepStates. You can\n specify a maximum of 10 stepIDs. The CLI automatically\n paginates results to return a list greater than 50 steps. To return more than 50 steps\n using the CLI, specify a Marker, which is a pagination token\n that indicates the next set of steps to retrieve.
The maximum number of steps that a single ListSteps action returns is 50. To return a longer list of steps, use multiple ListSteps actions along with the Marker parameter, which is a pagination token that indicates the next set of results to retrieve.
The maximum number of steps that a single ListSteps action returns is 50.\n To return a longer list of steps, use multiple ListSteps actions along with\n the Marker parameter, which is a pagination token that indicates the next set\n of results to retrieve.
The maximum number of steps that a single ListSteps action returns is 50. To return a longer list of steps, use multiple ListSteps actions along with the Marker parameter, which is a pagination token that indicates the next set of results to retrieve.
The maximum number of steps that a single ListSteps action returns is 50.\n To return a longer list of steps, use multiple ListSteps actions along with\n the Marker parameter, which is a pagination token that indicates the next set\n of results to retrieve.
Returns a list of all user or group session mappings for the Amazon EMR Studio specified by\n StudioId.
Returns a list of all user or group session mappings for the Amazon EMR Studio\n specified by StudioId.
A list of session mapping summary objects. Each object includes session mapping details\n such as creation time, identity type (user or group), and Amazon EMR Studio ID.
" + "smithy.api#documentation": "A list of session mapping summary objects. Each object includes session mapping details\n such as creation time, identity type (user or group), and Amazon EMR Studio\n ID.
" } }, "Marker": { @@ -5404,7 +5431,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns a list of all Amazon EMR Studios associated with the Amazon Web Services account. The list\n includes details such as ID, Studio Access URL, and creation time for each Studio.
", + "smithy.api#documentation": "Returns a list of all Amazon EMR Studios associated with the Amazon Web Services account. The list includes details such as ID, Studio Access URL, and\n creation time for each Studio.
", "smithy.api#paginated": { "inputToken": "Marker", "outputToken": "Marker", @@ -5454,7 +5481,7 @@ } }, "traits": { - "smithy.api#documentation": "Managed scaling policy for an Amazon EMR cluster. The policy specifies the limits for\n resources that can be added or terminated from a cluster. The policy only applies to the\n core and task nodes. The master node cannot be scaled after initial configuration.
" + "smithy.api#documentation": "Managed scaling policy for an Amazon EMR cluster. The policy specifies the\n limits for resources that can be added or terminated from a cluster. The policy only\n applies to the core and task nodes. The master node cannot be scaled after initial\n configuration.
" } }, "com.amazonaws.emr#Marker": { @@ -5502,7 +5529,7 @@ } }, "traits": { - "smithy.api#documentation": "A CloudWatch dimension, which is specified using a Key (known as a\n Name in CloudWatch), Value pair. By default, Amazon EMR uses\n one dimension whose Key is JobFlowID and Value is a\n variable representing the cluster ID, which is ${emr.clusterId}. This enables\n the rule to bootstrap when the cluster ID becomes available.
A CloudWatch dimension, which is specified using a Key (known as a\n Name in CloudWatch), Value pair. By default, Amazon EMR uses one dimension whose Key is JobFlowID and\n Value is a variable representing the cluster ID, which is\n ${emr.clusterId}. This enables the rule to bootstrap when the cluster ID\n becomes available.
The number of steps that can be executed concurrently. You can specify a minimum of 1 step and a maximum of 256 steps. We recommend that you do not change this parameter while steps are running or the ActionOnFailure setting may not behave as expected. For more information see Step$ActionOnFailure.
The number of steps that can be executed concurrently. You can specify a minimum of 1\n step and a maximum of 256 steps. We recommend that you do not change this parameter while\n steps are running or the ActionOnFailure setting may not behave as expected.\n For more information see Step$ActionOnFailure.
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 versions 4.8.0 and\n 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 versions\n 4.8.0 and later, excluding 5.0.x versions.
\nDetails for a notebook execution. The details include information such as the unique ID and status of the notebook execution.
" + "smithy.api#documentation": "Details for a notebook execution. The details include information such as the unique ID\n and status of the notebook execution.
" } }, "com.amazonaws.emr#NotebookExecutionSummaryList": { @@ -5828,19 +5861,39 @@ "target": "com.amazonaws.emr#NotebookExecutionSummary" } }, + "com.amazonaws.emr#OSRelease": { + "type": "structure", + "members": { + "Label": { + "target": "com.amazonaws.emr#String", + "traits": { + "smithy.api#documentation": "The Amazon Linux release specified for a cluster in the RunJobFlow request. The format is as shown in \n Amazon Linux 2 Release Notes\n . For example, 2.0.20220218.1.
" + } + } + }, + "traits": { + "smithy.api#documentation": "The Amazon Linux release specified for a cluster in the RunJobFlow request.
" + } + }, + "com.amazonaws.emr#OSReleaseList": { + "type": "list", + "member": { + "target": "com.amazonaws.emr#OSRelease" + } + }, "com.amazonaws.emr#OnDemandCapacityReservationOptions": { "type": "structure", "members": { "UsageStrategy": { "target": "com.amazonaws.emr#OnDemandCapacityReservationUsageStrategy", "traits": { - "smithy.api#documentation": "Indicates whether to use unused Capacity Reservations for fulfilling On-Demand capacity.
\nIf you specify use-capacity-reservations-first, the fleet uses unused Capacity Reservations to fulfill On-Demand capacity up to the target On-Demand capacity. If multiple instance pools have unused Capacity Reservations, the On-Demand allocation strategy (lowest-price) is applied. If the number of unused Capacity Reservations is less than the On-Demand target capacity, the remaining On-Demand target capacity is launched according to the On-Demand allocation strategy (lowest-price).
If you do not specify a value, the fleet fulfills the On-Demand capacity according to the chosen On-Demand allocation strategy.
" + "smithy.api#documentation": "Indicates whether to use unused Capacity Reservations for fulfilling On-Demand\n capacity.
\nIf you specify use-capacity-reservations-first, the fleet uses unused\n Capacity Reservations to fulfill On-Demand capacity up to the target On-Demand capacity. If\n multiple instance pools have unused Capacity Reservations, the On-Demand allocation\n strategy (lowest-price) is applied. If the number of unused Capacity\n Reservations is less than the On-Demand target capacity, the remaining On-Demand target\n capacity is launched according to the On-Demand allocation strategy\n (lowest-price).
If you do not specify a value, the fleet fulfills the On-Demand capacity according to\n the chosen On-Demand allocation strategy.
" } }, "CapacityReservationPreference": { "target": "com.amazonaws.emr#OnDemandCapacityReservationPreference", "traits": { - "smithy.api#documentation": "Indicates the instance's Capacity Reservation preferences. Possible preferences include:
\n\n open - The instance can run in any open Capacity Reservation that has matching attributes (instance type, platform, Availability Zone).
\n none - The instance avoids running in a Capacity Reservation even if one is available. The instance runs as an On-Demand Instance.
Indicates the instance's Capacity Reservation preferences. Possible preferences\n include:
\n\n open - The instance can run in any open Capacity Reservation that has\n matching attributes (instance type, platform, Availability Zone).
\n none - The instance avoids running in a Capacity Reservation even if\n one is available. The instance runs as an On-Demand Instance.
Describes the strategy for using unused Capacity Reservations for fulfilling On-Demand capacity.
" + "smithy.api#documentation": "Describes the strategy for using unused Capacity Reservations for fulfilling On-Demand\n capacity.
" } }, "com.amazonaws.emr#OnDemandCapacityReservationPreference": { @@ -5897,19 +5950,19 @@ "AllocationStrategy": { "target": "com.amazonaws.emr#OnDemandProvisioningAllocationStrategy", "traits": { - "smithy.api#documentation": "Specifies the strategy to use in launching On-Demand instance fleets. Currently, the only option is lowest-price (the default), which launches the lowest price first.
Specifies the strategy to use in launching On-Demand instance fleets. Currently, the\n only option is lowest-price (the default), which launches the lowest price\n first.
The launch specification for On-Demand instances in the instance fleet, which determines the allocation strategy.
" + "smithy.api#documentation": "The launch specification for On-Demand instances in the instance fleet, which determines\n the allocation strategy.
" } } }, "traits": { - "smithy.api#documentation": "The 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 versions 4.8.0 and\n later, excluding 5.0.x versions. On-Demand Instances allocation strategy is available in\n Amazon EMR version 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 versions\n 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is\n available in Amazon EMR version 5.12.1 and later.
\nEC2 Placement Group strategy associated with instance role.
\nStarting with Amazon EMR version 5.23.0, the only supported placement strategy is\n SPREAD for the MASTER instance role.
EC2 Placement Group strategy associated with instance role.
\nStarting with Amazon EMR version 5.23.0, the only supported placement strategy\n is SPREAD for the MASTER instance role.
Placement group configuration for an Amazon EMR cluster. The configuration specifies the\n placement strategy that can be applied to instance roles during cluster creation.
\nTo use this configuration, consider attaching managed policy\n AmazonElasticMapReducePlacementGroupPolicy to the EMR role.
" + "smithy.api#documentation": "Placement group configuration for an Amazon EMR cluster. The configuration\n specifies the placement strategy that can be applied to instance roles during cluster\n creation.
\nTo use this configuration, consider attaching managed policy\n AmazonElasticMapReducePlacementGroupPolicy to the EMR role.
" } }, "com.amazonaws.emr#PlacementGroupConfigList": { @@ -5977,13 +6030,13 @@ "AvailabilityZone": { "target": "com.amazonaws.emr#XmlString", "traits": { - "smithy.api#documentation": "The Amazon EC2 Availability Zone for the cluster. AvailabilityZone is used\n for uniform instance groups, while AvailabilityZones (plural) is used for\n instance fleets.
The Amazon EC2 Availability Zone for the cluster. AvailabilityZone\n is used for uniform instance groups, while AvailabilityZones (plural) is used\n for instance fleets.
When multiple Availability Zones are specified, Amazon EMR evaluates them and launches\n instances in the optimal Availability Zone. AvailabilityZones is used for\n instance fleets, while AvailabilityZone (singular) is used for uniform\n instance groups.
The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and\n 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 versions\n 4.8.0 and later, excluding 5.0.x versions.
\nCreates or updates an automatic scaling policy for a core instance group or task\n instance group in an Amazon EMR cluster. The automatic scaling policy defines how an\n instance group dynamically adds and terminates EC2 instances in response to the value of a\n CloudWatch metric.
" + "smithy.api#documentation": "Creates or updates an automatic scaling policy for a core instance group or task\n instance group in an Amazon EMR cluster. The automatic scaling policy defines how\n an instance group dynamically adds and terminates EC2 instances in response to the value of\n a CloudWatch metric.
" } }, "com.amazonaws.emr#PutAutoScalingPolicyInput": { @@ -6104,7 +6157,7 @@ "target": "com.amazonaws.emr#PutAutoTerminationPolicyOutput" }, "traits": { - "smithy.api#documentation": "Auto-termination is supported in Amazon EMR versions 5.30.0 and 6.1.0 and later. For more information, see Using an auto-termination policy.
\nCreates or updates an auto-termination policy for an Amazon EMR cluster. An auto-termination policy defines the amount of idle time in seconds after which a cluster automatically terminates. For alternative cluster termination options, see Control cluster termination.
" + "smithy.api#documentation": "Auto-termination is supported in Amazon EMR versions 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.
" } }, "com.amazonaws.emr#PutAutoTerminationPolicyInput": { @@ -6113,7 +6166,7 @@ "ClusterId": { "target": "com.amazonaws.emr#ClusterId", "traits": { - "smithy.api#documentation": "Specifies the ID of the Amazon EMR cluster to which the auto-termination policy will be attached.
", + "smithy.api#documentation": "Specifies the ID of the Amazon EMR cluster to which the auto-termination policy\n will be attached.
", "smithy.api#required": {} } }, @@ -6146,7 +6199,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates or updates an Amazon EMR block public access configuration for your Amazon Web Services account\n in the current Region. For more information see Configure Block\n Public Access for Amazon EMR in the Amazon EMR Management\n Guide.
" + "smithy.api#documentation": "Creates or updates an Amazon EMR block public access configuration for your\n Amazon Web Services account in the current Region. For more information see Configure Block\n Public Access for Amazon EMR in the Amazon EMR\n Management Guide.
" } }, "com.amazonaws.emr#PutBlockPublicAccessConfigurationInput": { @@ -6155,7 +6208,7 @@ "BlockPublicAccessConfiguration": { "target": "com.amazonaws.emr#BlockPublicAccessConfiguration", "traits": { - "smithy.api#documentation": "A configuration for Amazon EMR block public access. The configuration applies to all\n 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\n BlockPublicSecurityGroupRules 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 EMR cluster in a Region\n before this date, block public access is enabled by default in that 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. You can change this by updating\n BlockPublicSecurityGroupRules 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 EMR cluster in a Region\n before this date, block public access is enabled by default in that Region.
\nCreates or updates a managed scaling policy for an Amazon EMR cluster. The managed\n scaling policy defines the limits for resources, such as EC2 instances that can be added or\n terminated from a cluster. The policy only applies to the core and task nodes. The master\n node cannot be scaled after initial configuration.
" + "smithy.api#documentation": "Creates or updates a managed scaling policy for an Amazon EMR cluster. The\n managed scaling policy defines the limits for resources, such as EC2 instances that can be\n added or terminated from a cluster. The policy only applies to the core and task nodes. The\n master node cannot be scaled after initial configuration.
" } }, "com.amazonaws.emr#PutManagedScalingPolicyInput": { @@ -6200,6 +6253,21 @@ "type": "structure", "members": {} }, + "com.amazonaws.emr#ReconfigurationType": { + "type": "string", + "traits": { + "smithy.api#enum": [ + { + "value": "OVERWRITE", + "name": "OVERWRITE" + }, + { + "value": "MERGE", + "name": "MERGE" + } + ] + } + }, "com.amazonaws.emr#ReleaseLabelFilter": { "type": "structure", "members": { @@ -6273,7 +6341,7 @@ "ClusterId": { "target": "com.amazonaws.emr#ClusterId", "traits": { - "smithy.api#documentation": "Specifies the ID of the Amazon EMR cluster from which the auto-termination policy will be removed.
", + "smithy.api#documentation": "Specifies the ID of the Amazon EMR cluster from which the auto-termination\n policy will be removed.
", "smithy.api#required": {} } } @@ -6328,7 +6396,7 @@ } ], "traits": { - "smithy.api#documentation": "Removes tags from an Amazon EMR resource, such as a cluster or Amazon EMR Studio. Tags make it easier to associate resources in\n various ways, such as grouping clusters to track your Amazon EMR resource allocation costs.\n For more information, see Tag Clusters.
\nThe following example removes the stack tag with value Prod from a cluster:
" + "smithy.api#documentation": "Removes tags from an Amazon EMR resource, such as a cluster or Amazon EMR Studio. Tags make it easier to associate resources in various ways, such as grouping\n clusters to track your Amazon EMR resource allocation costs. For more information,\n see Tag\n Clusters.
\nThe following example removes the stack tag with value Prod from a cluster:
" } }, "com.amazonaws.emr#RemoveTagsInput": { @@ -6337,7 +6405,7 @@ "ResourceId": { "target": "com.amazonaws.emr#ResourceId", "traits": { - "smithy.api#documentation": "The Amazon EMR resource identifier from which tags will be removed. For example, a\n cluster identifier or an Amazon EMR Studio ID.
", + "smithy.api#documentation": "The Amazon EMR resource identifier from which tags will be removed. For example,\n a cluster identifier or an Amazon EMR Studio ID.
", "smithy.api#required": {} } }, @@ -6350,7 +6418,7 @@ } }, "traits": { - "smithy.api#documentation": "This input identifies an Amazon EMR resource and a list of tags to remove.
" + "smithy.api#documentation": "This input identifies an Amazon EMR resource and a list of tags to\n remove.
" } }, "com.amazonaws.emr#RemoveTagsOutput": { @@ -6392,7 +6460,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 Hadoop. For\n more information on how to do this, see Add More than 256 Steps to a\n Cluster in the Amazon EMR Management Guide.
\nFor long running clusters, we recommend that you periodically store your results.
\nThe instance fleets configuration is available only in Amazon EMR versions 4.8.0 and\n later, excluding 5.0.x versions. The RunJobFlow request can contain InstanceFleets\n 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 Hadoop. For\n more information on how to do this, see Add More than 256 Steps to a\n Cluster in the Amazon EMR Management Guide.
\nFor long running clusters, we recommend that you periodically store your results.
\nThe instance fleets configuration is available only in Amazon EMR versions\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.
\nThe location in Amazon S3 to write the log files of the job flow. If a value is not\n provided, logs are not created.
" + "smithy.api#documentation": "The location in Amazon S3 to write the log files of the job flow. If a value is\n not provided, logs are not created.
" } }, "LogEncryptionKmsKeyId": { "target": "com.amazonaws.emr#XmlString", "traits": { - "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 version 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 version 5.30.0 and later, excluding Amazon EMR 6.0.0.
" } }, "AdditionalInfo": { @@ -6426,13 +6494,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 releases 4.0 and\n 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 later, ReleaseLabel is used. To specify a custom AMI, use\n CustomAmiID.
The Amazon EMR release label, which determines the version of open-source application\n packages installed on the cluster. Release labels are in the form emr-x.x.x,\n where x.x.x is an Amazon EMR release version such as emr-5.14.0. For more\n information about Amazon EMR release versions and included application versions and\n features, see https://docs.aws.amazon.com/emr/latest/ReleaseGuide/. The release\n label applies only to Amazon EMR releases version 4.0 and later. Earlier versions use\n 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 later. Earlier versions use AmiVersion.
For Amazon EMR releases 3.x and 2.x. For Amazon EMR releases 4.x and later, use\n Applications.
\nA list of strings that indicates third-party software to use. For more information, see\n the Amazon EMR\n 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. 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 later, use\n Applications.
\nA list of strings that indicates third-party software to use with the job flow that\n accepts a user argument list. EMR accepts and forwards the argument list to the\n corresponding installation script as bootstrap action arguments. For more information, see\n \"Launch a Job Flow on the MapR Distribution for Hadoop\" in the Amazon EMR Developer Guide. Supported\n 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 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. EMR accepts and forwards the argument list to the\n corresponding installation script as bootstrap action arguments. For more information, see\n \"Launch a Job Flow on the MapR Distribution for Hadoop\" in the Amazon EMR Developer Guide.\n 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 applications\n for Amazon EMR to install and configure when launching the cluster. For a list of\n applications available for each Amazon EMR release version, see the Amazon EMRRelease\n Guide.
" + "smithy.api#documentation": "Applies 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.
" } }, "Configurations": { "target": "com.amazonaws.emr#ConfigurationList", "traits": { - "smithy.api#documentation": "For Amazon EMR releases 4.0 and later. The list of configurations supplied for the EMR\n cluster you are creating.
" + "smithy.api#documentation": "For Amazon EMR releases 4.0 and later. The list of configurations supplied for\n the EMR cluster you are creating.
" } }, "VisibleToAllUsers": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "The VisibleToAllUsers parameter is no longer supported. By default, the value is set to true. Setting it to false now has no effect.
Set this value to true so that IAM principals in the Amazon Web Services account associated with the cluster can perform EMR actions on the cluster that their IAM policies allow. This value defaults to true for clusters created using the EMR API or the CLI create-cluster command.
When set to false, only the IAM principal that created the cluster and the Amazon Web Services account root user can perform EMR actions for the cluster, regardless of the IAM permissions policies attached to other IAM principals. For more information, see Understanding the EMR Cluster VisibleToAllUsers Setting in the Amazon EMRManagement Guide.
The VisibleToAllUsers parameter is no longer supported. By default, the value is set\n to true. Setting it to false now has no effect.
Set this value to true so that IAM principals in the Amazon Web Services account associated with the cluster can perform EMR actions on the cluster\n that their IAM policies allow. This value defaults to true for clusters\n created using the EMR API or the CLI\n create-cluster command.
When set to false, only the IAM principal that created the cluster and the\n Amazon Web Services account root user can perform EMR actions for the cluster, regardless\n of the IAM permissions policies attached to other IAM principals. For more information, see\n Understanding the EMR Cluster VisibleToAllUsers Setting in the\n Amazon EMRManagement Guide.
The IAM role that Amazon EMR assumes in order to access Amazon Web Services resources on\n your behalf.
" + "smithy.api#documentation": "The IAM role that Amazon EMR assumes in order to access Amazon Web Services\n resources on your behalf.
" } }, "Tags": { "target": "com.amazonaws.emr#TagList", "traits": { - "smithy.api#documentation": "A list of tags to associate with a cluster and propagate to Amazon EC2 instances.
" + "smithy.api#documentation": "A list of tags to associate with a cluster and propagate to Amazon EC2\n instances.
" } }, "SecurityConfiguration": { @@ -6517,19 +6585,19 @@ "ScaleDownBehavior": { "target": "com.amazonaws.emr#ScaleDownBehavior", "traits": { - "smithy.api#documentation": "Specifies 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 nodes at\n the instance-hour boundary, regardless of when the request to terminate the instance was\n submitted. This option is only available with Amazon EMR 5.1.0 and later and is the default\n for clusters created using that version. TERMINATE_AT_TASK_COMPLETION\n indicates that Amazon EMR adds nodes to a deny list and drains tasks from nodes before\n terminating the Amazon EC2 instances, regardless of the instance-hour boundary. With either\n behavior, Amazon EMR removes the least active nodes first and blocks instance termination\n if it could lead to HDFS corruption. TERMINATE_AT_TASK_COMPLETION available\n only in Amazon EMR version 4.1.0 and later, and is the default for versions of Amazon EMR\n 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 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 version 4.1.0 and later, and is the default for versions of Amazon EMR earlier than 5.1.0.
Available only in Amazon EMR version 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 cluster EC2\n instances. For more information about custom AMIs in Amazon EMR, see Using a Custom\n AMI in the Amazon EMR Management Guide. If omitted, the\n cluster uses the base Linux AMI for the ReleaseLabel specified. For Amazon EMR\n versions 2.x and 3.x, use AmiVersion instead.
For information about creating a custom AMI, see Creating an Amazon EBS-Backed\n 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 version 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 EC2 instances. For more information about custom AMIs in Amazon EMR, see\n Using a\n Custom AMI in the Amazon EMR Management Guide. If\n omitted, the cluster uses the base Linux AMI for the ReleaseLabel specified.\n For Amazon EMR versions 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 used for\n each EC2 instance. Available in Amazon EMR version 4.x and later.
" + "smithy.api#documentation": "The size, in GiB, of the Amazon EBS root device volume of the Linux AMI that is\n used for each EC2 instance. Available in Amazon EMR version 4.x and later.
" } }, "RepoUpgradeOnBoot": { @@ -6564,6 +6632,12 @@ }, "AutoTerminationPolicy": { "target": "com.amazonaws.emr#AutoTerminationPolicy" + }, + "OSReleaseLabel": { + "target": "com.amazonaws.emr#XmlStringMaxLen256", + "traits": { + "smithy.api#documentation": "Specifies a particular Amazon Linux release for all nodes in a cluster launch RunJobFlow request. If a release is not specified, Amazon EMR uses the latest validated Amazon Linux release for cluster launch.
" + } } }, "traits": { @@ -6775,13 +6849,13 @@ "IdentityName": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The name of the user or group. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference.
" + "smithy.api#documentation": "The name of the user or group. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference.
" } }, "IdentityType": { "target": "com.amazonaws.emr#IdentityType", "traits": { - "smithy.api#documentation": "Specifies whether the identity mapped to the Amazon EMR Studio is a user or a group.
" + "smithy.api#documentation": "Specifies whether the identity mapped to the Amazon EMR Studio is a user or a\n group.
" } }, "SessionPolicyArn": { @@ -6804,7 +6878,7 @@ } }, "traits": { - "smithy.api#documentation": "Details for an Amazon EMR Studio session mapping including creation time, user or group\n ID, Studio ID, and so on.
" + "smithy.api#documentation": "Details for an Amazon EMR Studio session mapping including creation time, user\n or group ID, Studio ID, and so on.
" } }, "com.amazonaws.emr#SessionMappingSummary": { @@ -6819,19 +6893,19 @@ "IdentityId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The globally unique identifier (GUID) of the user or group from the Amazon Web Services SSO Identity\n Store.
" + "smithy.api#documentation": "The globally unique identifier (GUID) of the user or group from the Amazon Web Services SSO\n Identity Store.
" } }, "IdentityName": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The name of the user or group. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference.
" + "smithy.api#documentation": "The name of the user or group. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference.
" } }, "IdentityType": { "target": "com.amazonaws.emr#IdentityType", "traits": { - "smithy.api#documentation": "Specifies whether the identity mapped to the Amazon EMR Studio is a user or a group.
" + "smithy.api#documentation": "Specifies whether the identity mapped to the Amazon EMR Studio is a user or a\n group.
" } }, "SessionPolicyArn": { @@ -6848,7 +6922,7 @@ } }, "traits": { - "smithy.api#documentation": "Details for an Amazon EMR Studio session mapping. The details do not include the time\n the session mapping was last modified.
" + "smithy.api#documentation": "Details for an Amazon EMR Studio session mapping. The details do not include the\n time the session mapping was last modified.
" } }, "com.amazonaws.emr#SessionMappingSummaryList": { @@ -6862,13 +6936,16 @@ "input": { "target": "com.amazonaws.emr#SetTerminationProtectionInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" } ], "traits": { - "smithy.api#documentation": "SetTerminationProtection locks a cluster (job flow) so the EC2 instances in the cluster\n cannot be terminated by user intervention, an API call, or in the event of a job-flow\n error. The cluster still terminates upon successful completion of the job flow. Calling\n SetTerminationProtection on a cluster is similar to calling the Amazon EC2\n DisableAPITermination API on all EC2 instances in a cluster.
\n SetTerminationProtection is used to prevent accidental termination of a\n cluster and to ensure that in the event of an error, the instances persist so that you can\n recover any data stored in their ephemeral instance storage.
To terminate a cluster that has been locked by setting\n SetTerminationProtection to true, you must first unlock the\n job flow by a subsequent call to SetTerminationProtection in which you set the\n value to false.
For more information, seeManaging Cluster\n Termination in the Amazon EMR Management Guide.
" + "smithy.api#documentation": "SetTerminationProtection locks a cluster (job flow) so the EC2 instances in the cluster\n cannot be terminated by user intervention, an API call, or in the event of a job-flow\n error. The cluster still terminates upon successful completion of the job flow. Calling\n SetTerminationProtection on a cluster is similar to calling the Amazon EC2\n DisableAPITermination API on all EC2 instances in a cluster.
\n SetTerminationProtection is used to prevent accidental termination of a\n cluster and to ensure that in the event of an error, the instances persist so that you can\n recover any data stored in their ephemeral instance storage.
To terminate a cluster that has been locked by setting\n SetTerminationProtection to true, you must first unlock the\n job flow by a subsequent call to SetTerminationProtection in which you set the\n value to false.
For more information, seeManaging Cluster\n Termination in the Amazon EMR Management Guide.
" } }, "com.amazonaws.emr#SetTerminationProtectionInput": { @@ -6884,7 +6961,7 @@ "TerminationProtected": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "A Boolean that indicates whether to protect the cluster and prevent the Amazon EC2\n instances in the cluster from shutting down due to API calls, user intervention, or\n job-flow error.
", + "smithy.api#documentation": "A Boolean that indicates whether to protect the cluster and prevent the Amazon EC2 instances in the cluster from shutting down due to API calls, user intervention, or\n job-flow error.
", "smithy.api#required": {} } } @@ -6898,13 +6975,16 @@ "input": { "target": "com.amazonaws.emr#SetVisibleToAllUsersInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" } ], "traits": { - "smithy.api#documentation": "The SetVisibleToAllUsers parameter is no longer supported. Your cluster may be visible to all users in your account.\n To restrict cluster access using an IAM policy, see Identity and Access Management for EMR.\n
\nSets the Cluster$VisibleToAllUsers value for an EMR cluster. When true, IAM principals in the\n Amazon Web Services account can perform EMR cluster actions that their IAM policies allow. When false, only the IAM principal that created the cluster and the Amazon Web Services account root user can perform EMR actions on the cluster, regardless of IAM permissions policies attached to other IAM principals.
This action works on running clusters. When you create a cluster, use the RunJobFlowInput$VisibleToAllUsers parameter.
\nFor more information, see Understanding the EMR Cluster VisibleToAllUsers Setting in the Amazon EMRManagement Guide.
" + "smithy.api#documentation": "The SetVisibleToAllUsers parameter is no longer supported. Your cluster may be\n visible to all users in your account. To restrict cluster access using an IAM policy, see Identity and Access\n Management for EMR.
\nSets the Cluster$VisibleToAllUsers value for an EMR cluster. When\n true, IAM principals in the Amazon Web Services account can perform EMR\n cluster actions that their IAM policies allow. When false, only\n the IAM principal that created the cluster and the Amazon Web Services account root user can\n perform EMR actions on the cluster, regardless of IAM permissions policies attached to\n other IAM principals.
This action works on running clusters. When you create a cluster, use the RunJobFlowInput$VisibleToAllUsers parameter.
\nFor more information, see Understanding the EMR Cluster VisibleToAllUsers Setting in the\n Amazon EMRManagement Guide.
" } }, "com.amazonaws.emr#SetVisibleToAllUsersInput": { @@ -6920,7 +7000,7 @@ "VisibleToAllUsers": { "target": "com.amazonaws.emr#Boolean", "traits": { - "smithy.api#documentation": "A value of true indicates that an IAM principal in the Amazon Web Services account can perform\n EMR actions on the cluster that the IAM policies attached to the principal allow. A\n value of false indicates that only the IAM principal that created the cluster and the Amazon Web Services root user can perform EMR actions on the cluster.
A value of true indicates that an IAM principal in the Amazon Web Services account can perform EMR actions on the cluster that the IAM policies attached\n to the principal allow. A value of false indicates that only the IAM principal\n that created the cluster and the Amazon Web Services root user can perform EMR actions on\n the cluster.
The defined duration for Spot Instances (also known as Spot blocks) in minutes. When\n specified, the Spot Instance does not terminate before the defined duration expires, and\n defined duration pricing for Spot Instances applies. Valid values are 60, 120, 180, 240,\n 300, or 360. The duration period starts as soon as a Spot Instance receives its instance\n ID. At the end of the duration, Amazon EC2 marks the Spot Instance for termination and\n provides a Spot Instance termination notice, which gives the instance a two-minute warning\n before it terminates.
\nSpot Instances with a defined duration (also known as Spot blocks) are no longer available to new customers from July 1, 2021. For customers who have previously used the feature, we will continue to support Spot Instances with a defined duration until December 31, 2022.\n
\nThe defined duration for Spot Instances (also known as Spot blocks) in minutes. When\n specified, the Spot Instance does not terminate before the defined duration expires, and\n defined duration pricing for Spot Instances applies. Valid values are 60, 120, 180, 240,\n 300, or 360. The duration period starts as soon as a Spot Instance receives its instance\n ID. At the end of the duration, Amazon EC2 marks the Spot Instance for termination\n and provides a Spot Instance termination notice, which gives the instance a two-minute\n warning before it terminates.
\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 versions 4.8.0 and\n later, excluding 5.0.x versions. Spot Instance allocation strategy is available in\n Amazon EMR version 5.12.1 and later.
\nSpot Instances with a defined duration (also known as Spot blocks) are no longer available to new customers from July 1, 2021. For customers who have previously used the feature, we will continue to support Spot Instances with a defined duration until December 31, 2022.\n
\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 versions\n 4.8.0 and later, excluding 5.0.x versions. Spot Instance allocation strategy is\n available in Amazon EMR version 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 name or ARN of the IAM role that is used as the service role for Amazon EMR (the EMR\n role) for the notebook execution.
", + "smithy.api#documentation": "The name or ARN of the IAM role that is used as the service role for Amazon EMR\n (the EMR role) for the notebook execution.
", "smithy.api#required": {} } }, @@ -7201,7 +7281,7 @@ "ActionOnFailure": { "target": "com.amazonaws.emr#ActionOnFailure", "traits": { - "smithy.api#documentation": "The action to take when the cluster step fails. Possible values are TERMINATE_CLUSTER,\n CANCEL_AND_WAIT, and CONTINUE. TERMINATE_JOB_FLOW is provided for backward compatibility.\n We recommend using TERMINATE_CLUSTER instead.
If a cluster's StepConcurrencyLevel is greater than 1, do not use AddJobFlowSteps to submit a step with this parameter set to CANCEL_AND_WAIT or TERMINATE_CLUSTER. The step is not submitted and the action fails with a message that the ActionOnFailure setting is not valid.
If you change a cluster's StepConcurrencyLevel to be greater than 1 while a step is running, the ActionOnFailure parameter may not behave as you expect. In this case, for a step that fails with this parameter set to CANCEL_AND_WAIT, pending steps and the running step are not canceled; for a step that fails with this parameter set to TERMINATE_CLUSTER, the cluster does not terminate.
The action to take when the cluster step fails. Possible values are\n TERMINATE_CLUSTER, CANCEL_AND_WAIT, and CONTINUE.\n TERMINATE_JOB_FLOW is provided for backward compatibility. We recommend\n using TERMINATE_CLUSTER instead.
If a cluster's StepConcurrencyLevel is greater than 1, do not\n use AddJobFlowSteps to submit a step with this parameter set to\n CANCEL_AND_WAIT or TERMINATE_CLUSTER. The step is not\n submitted and the action fails with a message that the ActionOnFailure setting\n is not valid.
If you change a cluster's StepConcurrencyLevel to be greater than 1 while a\n step is running, the ActionOnFailure parameter may not behave as you expect.\n In this case, for a step that fails with this parameter set to\n CANCEL_AND_WAIT, pending steps and the running step are not canceled; for a\n step that fails with this parameter set to TERMINATE_CLUSTER, the cluster does\n not terminate.
The action to take when the step fails. Use one of the following values:
\n\n TERMINATE_CLUSTER - Shuts down the cluster.
\n CANCEL_AND_WAIT - Cancels any pending steps and returns the cluster to the WAITING state.
\n CONTINUE - Continues to the next step in the queue.
\n TERMINATE_JOB_FLOW - Shuts down the cluster. TERMINATE_JOB_FLOW is provided for backward compatibility. We recommend using TERMINATE_CLUSTER instead.
If a cluster's StepConcurrencyLevel is greater than 1, do not use AddJobFlowSteps to submit a step with this parameter set to CANCEL_AND_WAIT or TERMINATE_CLUSTER. The step is not submitted and the action fails with a message that the ActionOnFailure setting is not valid.
If you change a cluster's StepConcurrencyLevel to be greater than 1 while a step is running, the ActionOnFailure parameter may not behave as you expect. In this case, for a step that fails with this parameter set to CANCEL_AND_WAIT, pending steps and the running step are not canceled; for a step that fails with this parameter set to TERMINATE_CLUSTER, the cluster does not terminate.
The action to take when the step fails. Use one of the following values:
\n\n TERMINATE_CLUSTER - Shuts down the cluster.
\n CANCEL_AND_WAIT - Cancels any pending steps and returns the cluster\n to the WAITING state.
\n CONTINUE - Continues to the next step in the queue.
\n TERMINATE_JOB_FLOW - Shuts down the cluster.\n TERMINATE_JOB_FLOW is provided for backward compatibility. We\n recommend using TERMINATE_CLUSTER instead.
If a cluster's StepConcurrencyLevel is greater than 1, do not\n use AddJobFlowSteps to submit a step with this parameter set to\n CANCEL_AND_WAIT or TERMINATE_CLUSTER. The step is not\n submitted and the action fails with a message that the ActionOnFailure setting\n is not valid.
If you change a cluster's StepConcurrencyLevel to be greater than 1 while a\n step is running, the ActionOnFailure parameter may not behave as you expect.\n In this case, for a step that fails with this parameter set to\n CANCEL_AND_WAIT, pending steps and the running step are not canceled; for a\n step that fails with this parameter set to TERMINATE_CLUSTER, the cluster does\n not terminate.
The action to take when the cluster step fails. Possible values are TERMINATE_CLUSTER,\n CANCEL_AND_WAIT, and CONTINUE. TERMINATE_JOB_FLOW is available for backward compatibility.
" + "smithy.api#documentation": "The action to take when the cluster step fails. Possible values are TERMINATE_CLUSTER,\n CANCEL_AND_WAIT, and CONTINUE. TERMINATE_JOB_FLOW is available for backward\n compatibility.
" } }, "Status": { @@ -7555,6 +7635,9 @@ "input": { "target": "com.amazonaws.emr#StopNotebookExecutionInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" @@ -7651,19 +7734,19 @@ "UserRole": { "target": "com.amazonaws.emr#XmlString", "traits": { - "smithy.api#documentation": "The name of the IAM role assumed by users logged in to the Amazon EMR Studio. A Studio only requires a UserRole when you use IAM authentication.
The name of the IAM role assumed by users logged in to the Amazon EMR Studio. A\n Studio only requires a UserRole when you use IAM\n authentication.
The ID of the Workspace security group associated with the Amazon EMR Studio. The\n Workspace security group allows outbound network traffic to resources in the Engine\n security group and to the internet.
" + "smithy.api#documentation": "The ID of the Workspace security group associated with the Amazon EMR Studio.\n The Workspace security group allows outbound network traffic to resources in the Engine\n security group and to the internet.
" } }, "EngineSecurityGroupId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The ID of the Engine security group associated with the Amazon EMR Studio. The Engine\n security group allows inbound network traffic from resources in the Workspace security\n group.
" + "smithy.api#documentation": "The ID of the Engine security group associated with the Amazon EMR Studio. The\n Engine security group allows inbound network traffic from resources in the Workspace\n security group.
" } }, "Url": { @@ -7681,13 +7764,13 @@ "DefaultS3Location": { "target": "com.amazonaws.emr#XmlString", "traits": { - "smithy.api#documentation": "The Amazon S3 location to back up Amazon EMR Studio Workspaces and notebook\n files.
" + "smithy.api#documentation": "The Amazon S3 location to back up Amazon EMR Studio Workspaces and\n notebook files.
" } }, "IdpAuthUrl": { "target": "com.amazonaws.emr#XmlString", "traits": { - "smithy.api#documentation": "Your identity provider's authentication endpoint. Amazon EMR Studio redirects federated users to this endpoint for authentication when logging in to a Studio with the Studio URL.
" + "smithy.api#documentation": "Your identity provider's authentication endpoint. Amazon EMR Studio redirects\n federated users to this endpoint for authentication when logging in to a Studio with the\n Studio URL.
" } }, "IdpRelayStateParameterName": { @@ -7704,7 +7787,7 @@ } }, "traits": { - "smithy.api#documentation": "Details for an Amazon EMR Studio including ID, creation time, name, and so on.
" + "smithy.api#documentation": "Details for an Amazon EMR Studio including ID, creation time, name, and so\n on.
" } }, "com.amazonaws.emr#StudioSummary": { @@ -7725,7 +7808,7 @@ "VpcId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The ID of the Virtual Private Cloud (Amazon VPC) associated with the Amazon EMR\n Studio.
" + "smithy.api#documentation": "The ID of the Virtual Private Cloud (Amazon VPC) associated with the Amazon EMR Studio.
" } }, "Description": { @@ -7754,7 +7837,7 @@ } }, "traits": { - "smithy.api#documentation": "Details for an Amazon EMR Studio, including ID, Name, VPC, and Description. The details\n do not include subnets, IAM roles, security groups, or tags associated with the\n Studio.
" + "smithy.api#documentation": "Details for an Amazon EMR Studio, including ID, Name, VPC, and Description. The\n details do not include subnets, IAM roles, security groups, or tags associated with the\n Studio.
" } }, "com.amazonaws.emr#StudioSummaryList": { @@ -7812,7 +7895,7 @@ } }, "traits": { - "smithy.api#documentation": "A key-value pair containing user-defined metadata that you can associate with an Amazon EMR resource. Tags make it easier to associate clusters in various ways, such as grouping\n clusters to track your Amazon EMR resource allocation costs. For more information, see\n Tag\n Clusters.
" + "smithy.api#documentation": "A key-value pair containing user-defined metadata that you can associate with an Amazon EMR resource. Tags make it easier to associate clusters in various ways, such as\n grouping clusters to track your Amazon EMR resource allocation costs. For more\n information, see Tag Clusters.
" } }, "com.amazonaws.emr#TagList": { @@ -7826,13 +7909,16 @@ "input": { "target": "com.amazonaws.emr#TerminateJobFlowsInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" } ], "traits": { - "smithy.api#documentation": "TerminateJobFlows shuts a list of clusters (job flows) down. When a job flow is shut\n down, any step not yet completed is canceled and the EC2 instances on which the cluster is\n running are stopped. Any log files not already saved are uploaded to Amazon S3 if a LogUri\n was specified when the cluster was created.
\nThe maximum number of clusters allowed is 10. The call to TerminateJobFlows\n is asynchronous. Depending on the configuration of the cluster, it may take up to 1-5\n minutes for the cluster to completely terminate and release allocated resources, such as\n Amazon EC2 instances.
TerminateJobFlows shuts a list of clusters (job flows) down. When a job flow is shut\n down, any step not yet completed is canceled and the EC2 instances on which the cluster is\n running are stopped. Any log files not already saved are uploaded to Amazon S3 if a\n LogUri was specified when the cluster was created.
\nThe maximum number of clusters allowed is 10. The call to TerminateJobFlows\n is asynchronous. Depending on the configuration of the cluster, it may take up to 1-5\n minutes for the cluster to completely terminate and release allocated resources, such as\n Amazon EC2 instances.
Updates an Amazon EMR Studio configuration, including attributes such as name, description, and subnets.
" + "smithy.api#documentation": "Updates an Amazon EMR Studio configuration, including attributes such as name,\n description, and subnets.
" } }, "com.amazonaws.emr#UpdateStudioInput": { @@ -8007,7 +8096,7 @@ "SubnetIds": { "target": "com.amazonaws.emr#SubnetIdList", "traits": { - "smithy.api#documentation": "A list of subnet IDs to associate with the Amazon EMR Studio. The list can include new subnet IDs, but must also include all of the subnet IDs previously associated with the Studio. The list order does not matter. A Studio can have a maximum of 5 subnets. The subnets must belong to the same VPC as the Studio.
" + "smithy.api#documentation": "A list of subnet IDs to associate with the Amazon EMR Studio. The list can\n include new subnet IDs, but must also include all of the subnet IDs previously associated\n with the Studio. The list order does not matter. A Studio can have a maximum of 5 subnets.\n The subnets must belong to the same VPC as the Studio.
" } }, "DefaultS3Location": { @@ -8023,6 +8112,9 @@ "input": { "target": "com.amazonaws.emr#UpdateStudioSessionMappingInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.emr#InternalServerError" @@ -8032,7 +8124,7 @@ } ], "traits": { - "smithy.api#documentation": "Updates the session policy attached to the user or group for the specified Amazon EMR\n Studio.
" + "smithy.api#documentation": "Updates the session policy attached to the user or group for the specified Amazon EMR Studio.
" } }, "com.amazonaws.emr#UpdateStudioSessionMappingInput": { @@ -8048,13 +8140,13 @@ "IdentityId": { "target": "com.amazonaws.emr#XmlStringMaxLen256", "traits": { - "smithy.api#documentation": "The globally unique identifier (GUID) of the user or group. For more information, see\n UserId and GroupId in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified.
The globally unique identifier (GUID) of the user or group. For more information, see\n UserId and GroupId in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified.
The name of the user or group to update. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API Reference.\n Either IdentityName or IdentityId must be specified.
The name of the user or group to update. For more information, see UserName and DisplayName in the Amazon Web Services SSO Identity Store API\n Reference. Either IdentityName or IdentityId must\n be specified.
This API reference provides descriptions, syntax, and other details about each of the\n actions and data types for Amazon Web Services Migration Hub Refactor Spaces (Refactor Spaces). The topic for each action shows the API\n request parameters and the response. Alternatively, you can use one of the Amazon Web Services SDKs to\n access an API that is tailored to the programming language or platform that you're using. For\n more information, see Amazon Web Services SDKs.
\n \nTo share Refactor Spaces environments with other Amazon Web Services accounts or with Organizations\n and their OUs, use Resource Access Manager's CreateResourceShare API. See CreateResourceShare in the Amazon Web Services RAM API Reference.
This API reference provides descriptions, syntax, and other details about each of the\n actions and data types for Amazon Web Services Migration Hub Refactor Spaces (Refactor Spaces). The topic for each action shows the API\n request parameters and the response. Alternatively, you can use one of the Amazon Web Services SDKs to\n access an API that is tailored to the programming language or platform that you're using. For\n more information, see Amazon Web Services SDKs.
\nTo share Refactor Spaces environments with other Amazon Web Services accounts or with Organizations\n and their OUs, use Resource Access Manager's CreateResourceShare API. See CreateResourceShare in the Amazon Web Services RAM API Reference.