@aws-sdk/client-auto-scaling 3.205.0 → 3.208.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.
Files changed (3) hide show
  1. package/dist-types/models/models_0.d.ts +85 -43
  2. package/package.json +36 -36
  3. package/CHANGELOG.md +0 -3292
package/dist-types/models/models_0.d.ts CHANGED
@@ -499,28 +499,40 @@ export interface LifecycleHookSpecification {
499
499
  */
500
500
  export interface InstancesDistribution {
501
501
  /**
502
- * <p>The order of the launch template overrides to use in fulfilling On-Demand capacity. </p>
503
- * <p>If you specify <code>lowest-price</code>, Amazon EC2 Auto Scaling uses price to determine the order,
504
- * launching the lowest price first. </p>
505
- * <p>If you specify <code>prioritized</code>, Amazon EC2 Auto Scaling uses the priority that you assigned
506
- * to each launch template override, launching the highest priority first. If all your
507
- * On-Demand capacity cannot be fulfilled using your highest priority instance, then
508
- * Amazon EC2 Auto Scaling launches the remaining capacity using the second priority instance type, and so
509
- * on.</p>
510
- * <p>Default: <code>lowest-price</code> for Auto Scaling groups that specify <a>InstanceRequirements</a> in the overrides and <code>prioritized</code> for
511
- * Auto Scaling groups that don't.</p>
512
- * <p>Valid values: <code>lowest-price</code> | <code>prioritized</code>
513
- * </p>
502
+ * <p>The allocation strategy to apply to your On-Demand Instances when they are launched.
503
+ * Possible instance types are determined by the launch template overrides that you
504
+ * specify.</p>
505
+ * <p>The following lists the valid values:</p>
506
+ * <dl>
507
+ * <dt>lowest-price</dt>
508
+ * <dd>
509
+ * <p>Uses price to determine which instance types are the highest priority,
510
+ * launching the lowest priced instance types within an Availability Zone
511
+ * first. This is the default value for Auto Scaling groups that specify <a>InstanceRequirements</a>. </p>
512
+ * </dd>
513
+ * <dt>prioritized</dt>
514
+ * <dd>
515
+ * <p>You set the order of instance types for the launch template overrides from
516
+ * highest to lowest priority (from first to last in the list). Amazon EC2 Auto Scaling
517
+ * launches your highest priority instance types first. If all your On-Demand
518
+ * capacity cannot be fulfilled using your highest priority instance type, then
519
+ * Amazon EC2 Auto Scaling launches the remaining capacity using the second priority instance
520
+ * type, and so on. This is the default value for Auto Scaling groups that don't
521
+ * specify <a>InstanceRequirements</a> and cannot be used for groups
522
+ * that do.</p>
523
+ * </dd>
524
+ * </dl>
514
525
  */
515
526
  OnDemandAllocationStrategy?: string;
516
527
  /**
517
528
  * <p>The minimum amount of the Auto Scaling group's capacity that must be fulfilled by On-Demand
518
529
  * Instances. This base portion is launched first as your group scales.</p>
519
- * <p>If you specify weights for the instance types in the overrides, the base capacity is
520
- * measured in the same unit of measurement as the instance types. If you specify <a>InstanceRequirements</a> in the overrides, the base capacity is measured in
521
- * the same unit of measurement as your group's desired capacity.</p>
522
- * <p>Default: <code>0</code>
523
- * </p>
530
+ * <p>This number has the same unit of measurement as the group's desired capacity. If you
531
+ * change the default unit of measurement (number of instances) by specifying weighted
532
+ * capacity values in your launch template overrides list, or by changing the default
533
+ * desired capacity type setting of the group, you must specify this number using the same
534
+ * unit of measurement.</p>
535
+ * <p>Default: 0</p>
524
536
  */
525
537
  OnDemandBaseCapacity?: number;
526
538
  /**
@@ -528,36 +540,59 @@ export interface InstancesDistribution {
528
540
  * capacity beyond <code>OnDemandBaseCapacity</code>. Expressed as a number (for example,
529
541
  * 20 specifies 20% On-Demand Instances, 80% Spot Instances). If set to 100, only On-Demand
530
542
  * Instances are used.</p>
531
- * <p>Default: <code>100</code>
532
- * </p>
543
+ * <p>Default: 100</p>
533
544
  */
534
545
  OnDemandPercentageAboveBaseCapacity?: number;
535
546
  /**
536
- * <p>Indicates how to allocate instances across Spot Instance pools. </p>
537
- * <p>If the allocation strategy is <code>lowest-price</code>, the Auto Scaling group launches
538
- * instances using the Spot pools with the lowest price, and evenly allocates your
539
- * instances across the number of Spot pools that you specify. </p>
540
- * <p>If the allocation strategy is <code>capacity-optimized</code> (recommended), the Auto Scaling
541
- * group launches instances using Spot pools that are optimally chosen based on the
542
- * available Spot capacity. Alternatively, you can use
543
- * <code>capacity-optimized-prioritized</code> and set the order of instance types in
544
- * the list of launch template overrides from highest to lowest priority (from first to
545
- * last in the list). Amazon EC2 Auto Scaling honors the instance type priorities on a best-effort basis
546
- * but optimizes for capacity first. </p>
547
- * <p>Default: <code>lowest-price</code>
548
- * </p>
549
- * <p>Valid values: <code>lowest-price</code> | <code>capacity-optimized</code> |
550
- * <code>capacity-optimized-prioritized</code>
551
- * </p>
547
+ * <p>The allocation strategy to apply to your Spot Instances when they are launched.
548
+ * Possible instance types are determined by the launch template overrides that you
549
+ * specify.</p>
550
+ * <p>The following lists the valid values:</p>
551
+ * <dl>
552
+ * <dt>capacity-optimized</dt>
553
+ * <dd>
554
+ * <p>Requests Spot Instances using pools that are optimally chosen based on the
555
+ * available Spot capacity. This strategy has the lowest risk of interruption.
556
+ * To give certain instance types a higher chance of launching first, use
557
+ * <code>capacity-optimized-prioritized</code>.</p>
558
+ * </dd>
559
+ * <dt>capacity-optimized-prioritized</dt>
560
+ * <dd>
561
+ * <p>You set the order of instance types for the launch template overrides from
562
+ * highest to lowest priority (from first to last in the list). Amazon EC2 Auto Scaling honors
563
+ * the instance type priorities on a best effort basis but optimizes for
564
+ * capacity first. Note that if the On-Demand allocation strategy is set to
565
+ * <code>prioritized</code>, the same priority is applied when fulfilling
566
+ * On-Demand capacity. This is not a valid value for Auto Scaling groups that specify
567
+ * <a>InstanceRequirements</a>.</p>
568
+ * </dd>
569
+ * <dt>lowest-price</dt>
570
+ * <dd>
571
+ * <p>Requests Spot Instances using the lowest priced pools within an
572
+ * Availability Zone, across the number of Spot pools that you specify for the
573
+ * <code>SpotInstancePools</code> property. To ensure that your desired
574
+ * capacity is met, you might receive Spot Instances from several pools. This
575
+ * is the default value, but it might lead to high interruption rates because
576
+ * this strategy only considers instance price and not available
577
+ * capacity.</p>
578
+ * </dd>
579
+ * <dt>price-capacity-optimized (recommended)</dt>
580
+ * <dd>
581
+ * <p>Amazon EC2 Auto Scaling identifies the pools with the highest capacity availability for
582
+ * the number of instances that are launching. This means that we will request
583
+ * Spot Instances from the pools that we believe have the lowest chance of
584
+ * interruption in the near term. Amazon EC2 Auto Scaling then requests Spot Instances from
585
+ * the lowest priced of these pools.</p>
586
+ * </dd>
587
+ * </dl>
552
588
  */
553
589
  SpotAllocationStrategy?: string;
554
590
  /**
555
591
  * <p>The number of Spot Instance pools across which to allocate your Spot Instances. The
556
592
  * Spot pools are determined from the different instance types in the overrides. Valid only
557
- * when the Spot allocation strategy is <code>lowest-price</code>. Value must be in the
558
- * range of 1–20.</p>
559
- * <p>Default: <code>2</code>
560
- * </p>
593
+ * when the <code>SpotAllocationStrategy</code> is <code>lowest-price</code>. Value must be
594
+ * in the range of 1–20.</p>
595
+ * <p>Default: 2</p>
561
596
  */
562
597
  SpotInstancePools?: number;
563
598
  /**
@@ -1152,6 +1187,11 @@ export interface Tag {
1152
1187
  export interface CreateAutoScalingGroupType {
1153
1188
  /**
1154
1189
  * <p>The name of the Auto Scaling group. This name must be unique per Region per account.</p>
1190
+ * <p>The name can contain any ASCII character 33 to 126 including most punctuation
1191
+ * characters, digits, and upper and lowercased letters.</p>
1192
+ * <note>
1193
+ * <p>You cannot use a colon (:) in the name.</p>
1194
+ * </note>
1155
1195
  */
1156
1196
  AutoScalingGroupName: string | undefined;
1157
1197
  /**
@@ -1255,8 +1295,9 @@ export interface CreateAutoScalingGroupType {
1255
1295
  * of an EC2 instance that has come into service and marking it unhealthy due to a failed
1256
1296
  * Elastic Load Balancing or custom health check. This is useful if your instances do not immediately pass
1257
1297
  * these health checks after they enter the <code>InService</code> state. For more
1258
- * information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html#health-check-grace-period">Health
1259
- * check grace period</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
1298
+ * information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/health-check-grace-period.html">Set the health check
1299
+ * grace period for an Auto Scaling group</a> in the
1300
+ * <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
1260
1301
  * <p>Default: <code>0</code> seconds</p>
1261
1302
  */
1262
1303
  HealthCheckGracePeriod?: number;
@@ -5479,8 +5520,9 @@ export interface UpdateAutoScalingGroupType {
5479
5520
  * of an EC2 instance that has come into service and marking it unhealthy due to a failed
5480
5521
  * Elastic Load Balancing or custom health check. This is useful if your instances do not immediately pass
5481
5522
  * these health checks after they enter the <code>InService</code> state. For more
5482
- * information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html#health-check-grace-period">Health
5483
- * check grace period</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
5523
+ * information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/health-check-grace-period.html">Set the health check
5524
+ * grace period for an Auto Scaling group</a> in the
5525
+ * <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
5484
5526
  */
5485
5527
  HealthCheckGracePeriod?: number;
5486
5528
  /**
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-auto-scaling",
3
3
  "description": "AWS SDK for JavaScript Auto Scaling Client for Node.js, Browser and React Native",
4
- "version": "3.205.0",
4
+ "version": "3.208.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -19,48 +19,48 @@
19
19
  "dependencies": {
20
20
  "@aws-crypto/sha256-browser": "2.0.0",
21
21
  "@aws-crypto/sha256-js": "2.0.0",
22
- "@aws-sdk/client-sts": "3.204.0",
23
- "@aws-sdk/config-resolver": "3.201.0",
24
- "@aws-sdk/credential-provider-node": "3.204.0",
25
- "@aws-sdk/fetch-http-handler": "3.204.0",
26
- "@aws-sdk/hash-node": "3.201.0",
27
- "@aws-sdk/invalid-dependency": "3.201.0",
28
- "@aws-sdk/middleware-content-length": "3.201.0",
29
- "@aws-sdk/middleware-endpoint": "3.201.0",
30
- "@aws-sdk/middleware-host-header": "3.201.0",
31
- "@aws-sdk/middleware-logger": "3.201.0",
32
- "@aws-sdk/middleware-recursion-detection": "3.201.0",
33
- "@aws-sdk/middleware-retry": "3.201.0",
34
- "@aws-sdk/middleware-serde": "3.201.0",
35
- "@aws-sdk/middleware-signing": "3.201.0",
36
- "@aws-sdk/middleware-stack": "3.201.0",
37
- "@aws-sdk/middleware-user-agent": "3.201.0",
38
- "@aws-sdk/node-config-provider": "3.201.0",
39
- "@aws-sdk/node-http-handler": "3.201.0",
40
- "@aws-sdk/protocol-http": "3.201.0",
41
- "@aws-sdk/smithy-client": "3.201.0",
42
- "@aws-sdk/types": "3.201.0",
43
- "@aws-sdk/url-parser": "3.201.0",
44
- "@aws-sdk/util-base64": "3.202.0",
45
- "@aws-sdk/util-base64-browser": "3.188.0",
46
- "@aws-sdk/util-base64-node": "3.201.0",
22
+ "@aws-sdk/client-sts": "3.208.0",
23
+ "@aws-sdk/config-resolver": "3.208.0",
24
+ "@aws-sdk/credential-provider-node": "3.208.0",
25
+ "@aws-sdk/fetch-http-handler": "3.208.0",
26
+ "@aws-sdk/hash-node": "3.208.0",
27
+ "@aws-sdk/invalid-dependency": "3.208.0",
28
+ "@aws-sdk/middleware-content-length": "3.208.0",
29
+ "@aws-sdk/middleware-endpoint": "3.208.0",
30
+ "@aws-sdk/middleware-host-header": "3.208.0",
31
+ "@aws-sdk/middleware-logger": "3.208.0",
32
+ "@aws-sdk/middleware-recursion-detection": "3.208.0",
33
+ "@aws-sdk/middleware-retry": "3.208.0",
34
+ "@aws-sdk/middleware-serde": "3.208.0",
35
+ "@aws-sdk/middleware-signing": "3.208.0",
36
+ "@aws-sdk/middleware-stack": "3.208.0",
37
+ "@aws-sdk/middleware-user-agent": "3.208.0",
38
+ "@aws-sdk/node-config-provider": "3.208.0",
39
+ "@aws-sdk/node-http-handler": "3.208.0",
40
+ "@aws-sdk/protocol-http": "3.208.0",
41
+ "@aws-sdk/smithy-client": "3.208.0",
42
+ "@aws-sdk/types": "3.208.0",
43
+ "@aws-sdk/url-parser": "3.208.0",
44
+ "@aws-sdk/util-base64": "3.208.0",
45
+ "@aws-sdk/util-base64-browser": "3.208.0",
46
+ "@aws-sdk/util-base64-node": "3.208.0",
47
47
  "@aws-sdk/util-body-length-browser": "3.188.0",
48
- "@aws-sdk/util-body-length-node": "3.201.0",
49
- "@aws-sdk/util-defaults-mode-browser": "3.201.0",
50
- "@aws-sdk/util-defaults-mode-node": "3.201.0",
51
- "@aws-sdk/util-endpoints": "3.202.0",
52
- "@aws-sdk/util-user-agent-browser": "3.201.0",
53
- "@aws-sdk/util-user-agent-node": "3.201.0",
48
+ "@aws-sdk/util-body-length-node": "3.208.0",
49
+ "@aws-sdk/util-defaults-mode-browser": "3.208.0",
50
+ "@aws-sdk/util-defaults-mode-node": "3.208.0",
51
+ "@aws-sdk/util-endpoints": "3.208.0",
52
+ "@aws-sdk/util-user-agent-browser": "3.208.0",
53
+ "@aws-sdk/util-user-agent-node": "3.208.0",
54
54
  "@aws-sdk/util-utf8-browser": "3.188.0",
55
- "@aws-sdk/util-utf8-node": "3.201.0",
56
- "@aws-sdk/util-waiter": "3.201.0",
55
+ "@aws-sdk/util-utf8-node": "3.208.0",
56
+ "@aws-sdk/util-waiter": "3.208.0",
57
57
  "fast-xml-parser": "4.0.11",
58
58
  "tslib": "^2.3.1"
59
59
  },
60
60
  "devDependencies": {
61
- "@aws-sdk/service-client-documentation-generator": "3.188.0",
61
+ "@aws-sdk/service-client-documentation-generator": "3.208.0",
62
62
  "@tsconfig/node14": "1.0.3",
63
- "@types/node": "^12.7.5",
63
+ "@types/node": "^14.14.31",
64
64
  "concurrently": "7.0.0",
65
65
  "downlevel-dts": "0.10.1",
66
66
  "rimraf": "3.0.2",