You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(client-batch): This release adds Batch support for configuration of multicontainer jobs in ECS, Fargate, and EKS. This support is available for all types of jobs, including both array jobs and multi-node parallel jobs.
* <p>Creates an Batch compute environment. You can create <code>MANAGED</code> or <code>UNMANAGED</code> compute
32
-
* environments. <code>MANAGED</code> compute environments can use Amazon EC2 or Fargate resources.
33
-
* <code>UNMANAGED</code> compute environments can only use EC2 resources.</p>
34
-
* <p>In a managed compute environment, Batch manages the capacity and instance types of the compute resources
35
-
* within the environment. This is based on the compute resource specification that you define or the <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html">launch template</a> that you
36
-
* specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot
37
-
* Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can
38
-
* optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a
39
-
* specified percentage of the On-Demand price.</p>
31
+
* <p>Creates an Batch compute environment. You can create <code>MANAGED</code> or
32
+
* <code>UNMANAGED</code> compute environments. <code>MANAGED</code> compute environments can
33
+
* use Amazon EC2 or Fargate resources. <code>UNMANAGED</code> compute environments can only use
34
+
* EC2 resources.</p>
35
+
* <p>In a managed compute environment, Batch manages the capacity and instance types of the
36
+
* compute resources within the environment. This is based on the compute resource specification
37
+
* that you define or the <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html">launch template</a> that you
38
+
* specify when you create the compute environment. Either, you can choose to use EC2 On-Demand
39
+
* Instances and EC2 Spot Instances. Or, you can use Fargate and Fargate Spot capacity in
40
+
* your managed compute environment. You can optionally set a maximum price so that Spot
41
+
* Instances only launch when the Spot Instance price is less than a specified percentage of the
42
+
* On-Demand price.</p>
40
43
* <note>
41
44
* <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>
42
45
* </note>
43
-
* <p>In an unmanaged compute environment, you can manage your own EC2 compute resources and have flexibility with how
44
-
* you configure your compute resources. For example, you can use custom AMIs. However, you must verify that each of
45
-
* your AMIs meet the Amazon ECS container instance AMI specification. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html">container instance AMIs</a> in the
46
-
* <i>Amazon Elastic Container Service Developer Guide</i>. After you created your unmanaged compute environment, you can use the <a>DescribeComputeEnvironments</a> operation to find the Amazon ECS cluster that's associated with it. Then, launch
47
-
* your container instances into that Amazon ECS cluster. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching an Amazon ECS container instance</a> in the
48
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
46
+
* <p>In an unmanaged compute environment, you can manage your own EC2 compute resources and
47
+
* have flexibility with how you configure your compute resources. For example, you can use
48
+
* custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance
49
+
* AMI specification. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html">container instance AMIs</a> in the
50
+
* <i>Amazon Elastic Container Service Developer Guide</i>. After you created your unmanaged compute environment,
51
+
* you can use the <a>DescribeComputeEnvironments</a> operation to find the Amazon ECS
52
+
* cluster that's associated with it. Then, launch your container instances into that Amazon ECS
53
+
* cluster. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching an Amazon ECS container
54
+
* instance</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
49
55
* <note>
50
-
* <p>To create a compute environment that uses EKS resources, the caller must have permissions to call
51
-
* <code>eks:DescribeCluster</code>.</p>
56
+
* <p>To create a compute environment that uses EKS resources, the caller must have
57
+
* permissions to call <code>eks:DescribeCluster</code>.</p>
52
58
* </note>
53
59
* <note>
54
-
* <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it
55
-
* also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is
56
-
* available. You're responsible for the management of the guest operating system. This includes any updates and
57
-
* security patches. You're also responsible for any additional application software or utilities that you install on
58
-
* the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete
59
-
* these steps:</p>
60
+
* <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's
61
+
* created. For example, it also doesn't update the AMIs in your compute environment when a
62
+
* newer version of the Amazon ECS optimized AMI is available. You're responsible for the management
63
+
* of the guest operating system. This includes any updates and security patches. You're also
64
+
* responsible for any additional application software or utilities that you install on the
65
+
* compute resources. There are two ways to use a new AMI for your Batch jobs. The original
66
+
* method is to complete these steps:</p>
60
67
* <ol>
61
68
* <li>
62
69
* <p>Create a new compute environment with the new AMI.</p>
* environments</a>. To use the enhanced updating of compute environments to update AMIs, follow these
77
-
* rules:</p>
81
+
* <p>In April 2022, Batch added enhanced support for updating compute environments. For
82
+
* more information, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute environments</a>.
83
+
* To use the enhanced updating of compute environments to update AMIs, follow these
84
+
* rules:</p>
78
85
* <ul>
79
86
* <li>
80
-
* <p>Either don't set the service role (<code>serviceRole</code>) parameter or set it to the <b>AWSBatchServiceRole</b> service-linked role.</p>
87
+
* <p>Either don't set the service role (<code>serviceRole</code>) parameter or set it to
88
+
* the <b>AWSBatchServiceRole</b> service-linked role.</p>
81
89
* </li>
82
90
* <li>
83
-
* <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to <code>BEST_FIT_PROGRESSIVE</code>,
84
-
* <code>SPOT_CAPACITY_OPTIMIZED</code>, or <code>SPOT_PRICE_CAPACITY_OPTIMIZED</code>.</p>
91
+
* <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to
92
+
* <code>BEST_FIT_PROGRESSIVE</code>, <code>SPOT_CAPACITY_OPTIMIZED</code>, or
93
+
* <code>SPOT_PRICE_CAPACITY_OPTIMIZED</code>.</p>
85
94
* </li>
86
95
* <li>
87
96
* <p>Set the update to latest image version (<code>updateToLatestImageVersion</code>)
* <p>Don't specify an AMI ID in <code>imageId</code>, <code>imageIdOverride</code> (in <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html">
104
+
* <p>Don't specify an AMI ID in <code>imageId</code>, <code>imageIdOverride</code> (in
* <p>Before you can delete a compute environment, you must set its state to <code>DISABLED</code> with the <a>UpdateComputeEnvironment</a> API operation and disassociate it from any job queues with the <a>UpdateJobQueue</a> API operation. Compute environments that use Fargate resources must terminate all
33
-
* active jobs on that compute environment before deleting the compute environment. If this isn't done, the compute
34
-
* environment enters an invalid state.</p>
32
+
* <p>Before you can delete a compute environment, you must set its state to
33
+
* <code>DISABLED</code> with the <a>UpdateComputeEnvironment</a> API operation and
34
+
* disassociate it from any job queues with the <a>UpdateJobQueue</a> API operation.
35
+
* Compute environments that use Fargate resources must terminate all active jobs on that
36
+
* compute environment before deleting the compute environment. If this isn't done, the compute
37
+
* environment enters an invalid state.</p>
35
38
* @example
36
39
* Use a bare-bones client and the command you need to make an API call.
* <p>Deletes the specified job queue. You must first disable submissions for a queue with the <a>UpdateJobQueue</a> operation. All jobs in the queue are eventually terminated when you delete a job queue.
32
-
* The jobs are terminated at a rate of about 16 jobs each second.</p>
31
+
* <p>Deletes the specified job queue. You must first disable submissions for a queue with the
32
+
* <a>UpdateJobQueue</a> operation. All jobs in the queue are eventually terminated
33
+
* when you delete a job queue. The jobs are terminated at a rate of about 16 jobs each
34
+
* second.</p>
33
35
* <p>It's not necessary to disassociate compute environments from a queue before submitting a
34
-
* <code>DeleteJobQueue</code> request.</p>
36
+
* <code>DeleteJobQueue</code> request.</p>
35
37
* @example
36
38
* Use a bare-bones client and the command you need to make an API call.
0 commit comments