aws-sdk-batch 1.61.0 → 1.62.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 7e4c51c8292e04a8fefb257e89ca7461e451cb76d427eef9f04f421920fd6034
4
- data.tar.gz: 5dd50fb327fa153ce41e5c7e8cf8a9ece78339010708cf54af11758d9c4c6ee1
3
+ metadata.gz: 317199b27dc25a34dff4de2ce56e5d3a68d411eb3e374f0b03ec8cda59f0660d
4
+ data.tar.gz: 2bc7a3dc1ce9a033a56e49e67db9eec33169c580af0e09a910ce55e242464d51
5
5
  SHA512:
6
- metadata.gz: 70daac93441258d0426c7c856f720db519f66ed2c16ba45fde54247502636b0f0c1ee5373c95bcac487c4b678a81b2d3f1c7d20e93420aa0c18ee8835a75bbdb
7
- data.tar.gz: bcef79db296232a7745d0db73d73bbb9a71bde4811e7fe2c05cc3f60170f57895140f762feea2a7e12e1534d499472018cca2153be7964f879784560a995a12d
6
+ metadata.gz: d6513e3677f754fdfe367b561af8ed19f9216e2feff6f54cdb114a1eb2ab3d336f4bfdf81a24b4c5b2ea33b934a826e87586f160b95c06fadd71c046911abccd
7
+ data.tar.gz: 110c21ae8ad99b6ceec6f0e1f0701d5ce045d915180e4d95b4f29e374ff1c72f131e15a12b6d03d4c7b3af681c24f24ebded238463dcddbbb44e71bc41181e9e
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.62.0 (2022-05-18)
5
+ ------------------
6
+
7
+ * Feature - Documentation updates for AWS Batch.
8
+
4
9
  1.61.0 (2022-04-14)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.61.0
1
+ 1.62.0
@@ -429,13 +429,15 @@ module Aws::Batch
429
429
  # [Launching an Amazon ECS container instance][3] in the *Amazon Elastic
430
430
  # Container Service Developer Guide*.
431
431
  #
432
- # <note markdown="1"> Batch doesn't upgrade the AMIs in a compute environment after the
433
- # environment is created. For example, it doesn't update the AMIs when
434
- # a newer version of the Amazon ECS optimized AMI is available.
435
- # Therefore, you're responsible for managing the guest operating system
436
- # (including its updates and security patches) and any additional
437
- # application software or utilities that you install on the compute
438
- # resources. To use a new AMI for your Batch jobs, complete these steps:
432
+ # <note markdown="1"> Batch doesn't automatically upgrade the AMIs in a compute environment
433
+ # after it's created. For example, it also doesn't update the AMIs in
434
+ # your compute environment when a newer version of the Amazon ECS
435
+ # optimized AMI is available. You're responsible for the management of
436
+ # the guest operating system. This includes any updates and security
437
+ # patches. You're also responsible for any additional application
438
+ # software or utilities that you install on the compute resources. There
439
+ # are two ways to use a new AMI for your Batch jobs. The original method
440
+ # is to complete these steps:
439
441
  #
440
442
  # 1. Create a new compute environment with the new AMI.
441
443
  #
@@ -445,6 +447,43 @@ module Aws::Batch
445
447
  #
446
448
  # 4. Delete the earlier compute environment.
447
449
  #
450
+ # In April 2022, Batch added enhanced support for updating compute
451
+ # environments. For more information, see [Updating compute
452
+ # environments][4]. To use the enhanced updating of compute environments
453
+ # to update AMIs, follow these rules:
454
+ #
455
+ # * Either do not set the service role (`serviceRole`) parameter or set
456
+ # it to the **AWSBatchServiceRole** service-linked role.
457
+ #
458
+ # * Set the allocation strategy (`allocationStrategy`) parameter to
459
+ # `BEST_FIT_PROGRESSIVE` or `SPOT_CAPACITY_OPTIMIZED`.
460
+ #
461
+ # * Set the update to latest image version
462
+ # (`updateToLatestImageVersion`) parameter to `true`.
463
+ #
464
+ # * Do not specify an AMI ID in `imageId`, `imageIdOverride` (in [
465
+ # `ec2Configuration` ][5]), or in the launch template
466
+ # (`launchTemplate`). In that case Batch will select the latest Amazon
467
+ # ECS optimized AMI supported by Batch at the time the infrastructure
468
+ # update is initiated. Alternatively you can specify the AMI ID in the
469
+ # `imageId` or `imageIdOverride` parameters, or the launch template
470
+ # identified by the `LaunchTemplate` properties. Changing any of these
471
+ # properties will trigger an infrastructure update. If the AMI ID is
472
+ # specified in the launch template, it can not be replaced by
473
+ # specifying an AMI ID in either the `imageId` or `imageIdOverride`
474
+ # parameters. It can only be replaced by specifying a different launch
475
+ # template, or if the launch template version is set to `$Default` or
476
+ # `$Latest`, by setting either a new default version for the launch
477
+ # template (if `$Default`)or by adding a new version to the launch
478
+ # template (if `$Latest`).
479
+ #
480
+ # If these rules are followed, any update that triggers an
481
+ # infrastructure update will cause the AMI ID to be re-selected. If the
482
+ # `version` setting in the launch template (`launchTemplate`) is set to
483
+ # `$Latest` or `$Default`, the latest or default version of the launch
484
+ # template will be evaluated up at the time of the infrastructure
485
+ # update, even if the `launchTemplate` was not updated.
486
+ #
448
487
  # </note>
449
488
  #
450
489
  #
@@ -452,6 +491,8 @@ module Aws::Batch
452
491
  # [1]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html
453
492
  # [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html
454
493
  # [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html
494
+ # [4]: https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html
495
+ # [5]: https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html
455
496
  #
456
497
  # @option params [required, String] :compute_environment_name
457
498
  # The name for your compute environment. It can be up to 128 letters
@@ -2647,7 +2688,10 @@ module Aws::Batch
2647
2688
  # name or the Amazon Resource Name (ARN) of the queue.
2648
2689
  #
2649
2690
  # @option params [String] :share_identifier
2650
- # The share identifier for the job.
2691
+ # The share identifier for the job. If the job queue does not have a
2692
+ # scheduling policy, then this parameter must not be specified. If the
2693
+ # job queue has a scheduling policy, then this parameter must be
2694
+ # specified.
2651
2695
  #
2652
2696
  # @option params [Integer] :scheduling_priority_override
2653
2697
  # The scheduling priority for the job. This will only affect jobs in job
@@ -3325,7 +3369,7 @@ module Aws::Batch
3325
3369
  params: params,
3326
3370
  config: config)
3327
3371
  context[:gem_name] = 'aws-sdk-batch'
3328
- context[:gem_version] = '1.61.0'
3372
+ context[:gem_version] = '1.62.0'
3329
3373
  Seahorse::Client::Request.new(handlers, context)
3330
3374
  end
3331
3375
 
@@ -627,16 +627,20 @@ module Aws::Batch
627
627
  # "String1": "String2", where String1 is the tag key and String2
628
628
  # is the tag value−for example, `\{ "Name": "Batch Instance -
629
629
  # C4OnDemand" \}`. This is helpful for recognizing your Batch
630
- # instances in the Amazon EC2 console. These tags can't be updated or
631
- # removed after the compute environment is created. Any changes to
632
- # these tags require that you create a new compute environment and
633
- # remove the old compute environment. These tags aren't seen when
634
- # using the Batch `ListTagsForResource` API operation.
630
+ # instances in the Amazon EC2 console. Updating these tags requires an
631
+ # infrastructure update to the compute environment. For more
632
+ # information, see [Updating compute environments][1] in the *Batch
633
+ # User Guide*. These tags aren't seen when using the Batch
634
+ # `ListTagsForResource` API operation.
635
635
  #
636
636
  # <note markdown="1"> This parameter isn't applicable to jobs that are running on Fargate
637
637
  # resources, and shouldn't be specified.
638
638
  #
639
639
  # </note>
640
+ #
641
+ #
642
+ #
643
+ # [1]: https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html
640
644
  # @return [Hash<String,String>]
641
645
  #
642
646
  # @!attribute [rw] placement_group
@@ -5879,7 +5883,10 @@ module Aws::Batch
5879
5883
  # @return [String]
5880
5884
  #
5881
5885
  # @!attribute [rw] share_identifier
5882
- # The share identifier for the job.
5886
+ # The share identifier for the job. If the job queue does not have a
5887
+ # scheduling policy, then this parameter must not be specified. If the
5888
+ # job queue has a scheduling policy, then this parameter must be
5889
+ # specified.
5883
5890
  # @return [String]
5884
5891
  #
5885
5892
  # @!attribute [rw] scheduling_priority_override
data/lib/aws-sdk-batch.rb CHANGED
@@ -48,6 +48,6 @@ require_relative 'aws-sdk-batch/customizations'
48
48
  # @!group service
49
49
  module Aws::Batch
50
50
 
51
- GEM_VERSION = '1.61.0'
51
+ GEM_VERSION = '1.62.0'
52
52
 
53
53
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-batch
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.61.0
4
+ version: 1.62.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2022-04-14 00:00:00.000000000 Z
11
+ date: 2022-05-18 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core