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
Copy file name to clipboardExpand all lines: lib/aws/generated/batch.ex
+3-79Lines changed: 3 additions & 79 deletions
Original file line number
Diff line number
Diff line change
@@ -2837,8 +2837,6 @@ defmodule AWS.Batch do
2837
2837
percentage of the
2838
2838
On-Demand price.
2839
2839
2840
-
Multi-node parallel jobs aren't supported on Spot Instances.
2841
-
2842
2840
In an unmanaged compute environment, you can manage your own EC2 compute
2843
2841
resources and
2844
2842
have flexibility with how you configure your compute resources. For example, you
@@ -2855,84 +2853,10 @@ defmodule AWS.Batch do
2855
2853
cluster. For more information, see [Launching an Amazon ECS container instance](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html)
2856
2854
in the *Amazon Elastic Container Service Developer Guide*.
2857
2855
2858
-
To create a compute environment that uses EKS resources, the caller must have
2859
-
permissions to call `eks:DescribeCluster`.
2860
-
2861
2856
Batch doesn't automatically upgrade the AMIs in a compute environment after it's
2862
-
created. For example, it also doesn't update the AMIs in your compute
2863
-
environment when a
2864
-
newer version of the Amazon ECS optimized AMI is available. You're responsible
2865
-
for the management
2866
-
of the guest operating system. This includes any updates and security patches.
2867
-
You're also
2868
-
responsible for any additional application software or utilities that you
2869
-
install on the
2870
-
compute resources. There are two ways to use a new AMI for your Batch jobs. The
2871
-
original
2872
-
method is to complete these steps:
2873
-
2874
-
2875
-
Create a new compute environment with the new AMI.
2876
-
2877
-
2878
-
Add the compute environment to an existing job queue.
2879
-
2880
-
2881
-
Remove the earlier compute environment from your job queue.
2882
-
2883
-
2884
-
Delete the earlier compute environment.
2885
-
2886
-
In April 2022, Batch added enhanced support for updating compute environments.
2887
-
For
2888
-
more information, see [Updating compute environments](https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html).
2889
-
To use the enhanced updating of compute environments to update AMIs, follow
2890
-
these
2891
-
rules:
2892
-
2893
-
2894
-
Either don't set the service role (`serviceRole`) parameter or set it to
2895
-
the **AWSBatchServiceRole** service-linked role.
2896
-
2897
-
2898
-
Set the allocation strategy (`allocationStrategy`) parameter to
2899
-
`BEST_FIT_PROGRESSIVE`, `SPOT_CAPACITY_OPTIMIZED`, or
2900
-
`SPOT_PRICE_CAPACITY_OPTIMIZED`.
2901
-
2902
-
2903
-
Set the update to latest image version (`updateToLatestImageVersion`)
2904
-
parameter to `true`. The `updateToLatestImageVersion` parameter
2905
-
is used when you update a compute environment. This parameter is ignored when
2906
-
you create
2907
-
a compute environment.
2908
-
2909
-
2910
-
Don't specify an AMI ID in `imageId`, `imageIdOverride` (in
0 commit comments