@@ -139,12 +139,11 @@ namespace Batch
139139 * can use Fargate and Fargate Spot capacity in your managed compute environment.
140140 * You can optionally set a maximum price so that Spot Instances only launch when
141141 * the Spot Instance price is less than a specified percentage of the On-Demand
142- * price.</p> <p>Multi-node parallel jobs aren't supported on Spot
143- * Instances.</p> <p>In an unmanaged compute environment, you can manage
144- * your own EC2 compute resources and have flexibility with how you configure your
145- * compute resources. For example, you can use custom AMIs. However, you must
146- * verify that each of your AMIs meet the Amazon ECS container instance AMI
147- * specification. For more information, see <a
142+ * price.</p> <p>In an unmanaged compute environment, you can manage your own EC2
143+ * compute resources and have flexibility with how you configure your compute
144+ * resources. For example, you can use custom AMIs. However, you must verify that
145+ * each of your AMIs meet the Amazon ECS container instance AMI specification. For
146+ * more information, see <a
148147 * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html">container
149148 * instance AMIs</a> in the <i>Amazon Elastic Container Service Developer
150149 * Guide</i>. After you created your unmanaged compute environment, you can use the
@@ -153,57 +152,12 @@ namespace Batch
153152 * Amazon ECS cluster. For more information, see <a
154153 * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching
155154 * an Amazon ECS container instance</a> in the <i>Amazon Elastic Container Service
156- * Developer Guide</i>.</p> <p>To create a compute environment that uses EKS
157- * resources, the caller must have permissions to call
158- * <code>eks:DescribeCluster</code>.</p> <p>Batch doesn't
159- * automatically upgrade the AMIs in a compute environment after it's created. For
160- * example, it also doesn't update the AMIs in your compute environment when a
161- * newer version of the Amazon ECS optimized AMI is available. You're responsible
162- * for the management of the guest operating system. This includes any updates and
163- * security patches. You're also responsible for any additional application
164- * software or utilities that you install on the compute resources. There are two
165- * ways to use a new AMI for your Batch jobs. The original method is to complete
166- * these steps:</p> <ol> <li> <p>Create a new compute environment with the new
167- * AMI.</p> </li> <li> <p>Add the compute environment to an existing job queue.</p>
168- * </li> <li> <p>Remove the earlier compute environment from your job queue.</p>
169- * </li> <li> <p>Delete the earlier compute environment.</p> </li> </ol> <p>In
170- * April 2022, Batch added enhanced support for updating compute environments. For
171- * more information, see <a
155+ * Developer Guide</i>.</p> <p>Batch doesn't automatically upgrade the AMIs
156+ * in a compute environment after it's created. For more information on how to
157+ * update a compute environment's AMI, see <a
172158 * href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating
173- * compute environments</a>. To use the enhanced updating of compute environments
174- * to update AMIs, follow these rules:</p> <ul> <li> <p>Either don't set the
175- * service role (<code>serviceRole</code>) parameter or set it to the
176- * <b>AWSBatchServiceRole</b> service-linked role.</p> </li> <li> <p>Set the
177- * allocation strategy (<code>allocationStrategy</code>) parameter to
178- * <code>BEST_FIT_PROGRESSIVE</code>, <code>SPOT_CAPACITY_OPTIMIZED</code>, or
179- * <code>SPOT_PRICE_CAPACITY_OPTIMIZED</code>.</p> </li> <li> <p>Set the update to
180- * latest image version (<code>updateToLatestImageVersion</code>) parameter to
181- * <code>true</code>. The <code>updateToLatestImageVersion</code> parameter is used
182- * when you update a compute environment. This parameter is ignored when you create
183- * a compute environment.</p> </li> <li> <p>Don't specify an AMI ID in
184- * <code>imageId</code>, <code>imageIdOverride</code> (in <a
185- * href="https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html">
186- * <code>ec2Configuration</code> </a>), or in the launch template
187- * (<code>launchTemplate</code>). In that case, Batch selects the latest Amazon ECS
188- * optimized AMI that's supported by Batch at the time the infrastructure update is
189- * initiated. Alternatively, you can specify the AMI ID in the <code>imageId</code>
190- * or <code>imageIdOverride</code> parameters, or the launch template identified by
191- * the <code>LaunchTemplate</code> properties. Changing any of these properties
192- * starts an infrastructure update. If the AMI ID is specified in the launch
193- * template, it can't be replaced by specifying an AMI ID in either the
194- * <code>imageId</code> or <code>imageIdOverride</code> parameters. It can only be
195- * replaced by specifying a different launch template, or if the launch template
196- * version is set to <code>$Default</code> or <code>$Latest</code>, by setting
197- * either a new default version for the launch template (if <code>$Default</code>)
198- * or by adding a new version to the launch template (if <code>$Latest</code>).</p>
199- * </li> </ul> <p>If these rules are followed, any update that starts an
200- * infrastructure update causes the AMI ID to be re-selected. If the
201- * <code>version</code> setting in the launch template
202- * (<code>launchTemplate</code>) is set to <code>$Latest</code> or
203- * <code>$Default</code>, the latest or default version of the launch template is
204- * evaluated up at the time of the infrastructure update, even if the
205- * <code>launchTemplate</code> wasn't updated.</p> <p><h3>See Also:</h3>
206- * <a
159+ * compute environments</a> in the <i>Batch User Guide</i>.</p> <p><h3>See
160+ * Also:</h3> <a
207161 * href="http://docs.aws.amazon.com/goto/WebAPI/batch-2016-08-10/CreateComputeEnvironment">AWS
208162 * API Reference</a></p>
209163 */
0 commit comments