aws-sdk 2.288.0 → 2.292.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.
package/clients/rds.d.ts CHANGED
@@ -533,6 +533,14 @@ declare class RDS extends Service {
533
533
  * Lists all tags on an Amazon RDS resource. For an overview on tagging an Amazon RDS resource, see Tagging Amazon RDS Resources.
534
534
  */
535
535
  listTagsForResource(callback?: (err: AWSError, data: RDS.Types.TagListMessage) => void): Request<RDS.Types.TagListMessage, AWSError>;
536
+ /**
537
+ * Set the capacity of an Aurora Serverless DB cluster to a specific value. Aurora Serverless scales seamlessly based on the workload on the DB cluster. In some cases, the capacity might not scale fast enough to meet a sudden change in workload, such as a large number of new transactions. Call ModifyCurrentDBClusterCapacity to set the capacity explicitly. After this call sets the DB cluster capacity, Aurora Serverless can automatically scale the DB cluster based on the cooldown period for scaling up and the cooldown period for scaling down. For more information about Aurora Serverless, see Using Amazon Aurora Serverless in the Amazon RDS User Guide. If you call ModifyCurrentDBClusterCapacity with the default TimeoutAction, connections that prevent Aurora Serverless from finding a scaling point might be dropped. For more information about scaling points, see Autoscaling for Aurora Serverless in the Amazon RDS User Guide.
538
+ */
539
+ modifyCurrentDBClusterCapacity(params: RDS.Types.ModifyCurrentDBClusterCapacityMessage, callback?: (err: AWSError, data: RDS.Types.DBClusterCapacityInfo) => void): Request<RDS.Types.DBClusterCapacityInfo, AWSError>;
540
+ /**
541
+ * Set the capacity of an Aurora Serverless DB cluster to a specific value. Aurora Serverless scales seamlessly based on the workload on the DB cluster. In some cases, the capacity might not scale fast enough to meet a sudden change in workload, such as a large number of new transactions. Call ModifyCurrentDBClusterCapacity to set the capacity explicitly. After this call sets the DB cluster capacity, Aurora Serverless can automatically scale the DB cluster based on the cooldown period for scaling up and the cooldown period for scaling down. For more information about Aurora Serverless, see Using Amazon Aurora Serverless in the Amazon RDS User Guide. If you call ModifyCurrentDBClusterCapacity with the default TimeoutAction, connections that prevent Aurora Serverless from finding a scaling point might be dropped. For more information about scaling points, see Autoscaling for Aurora Serverless in the Amazon RDS User Guide.
542
+ */
543
+ modifyCurrentDBClusterCapacity(callback?: (err: AWSError, data: RDS.Types.DBClusterCapacityInfo) => void): Request<RDS.Types.DBClusterCapacityInfo, AWSError>;
536
544
  /**
537
545
  * Modify a setting for an Amazon Aurora DB cluster. You can change one or more database configuration parameters by specifying these parameters and the new values in the request. For more information on Amazon Aurora, see Aurora on Amazon RDS in the Amazon RDS User Guide.
538
546
  */
@@ -1201,9 +1209,17 @@ declare namespace RDS {
1201
1209
  */
1202
1210
  BacktrackWindow?: LongOptional;
1203
1211
  /**
1204
- * The list of log types that need to be enabled for exporting to CloudWatch Logs.
1212
+ * The list of log types that need to be enabled for exporting to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
1205
1213
  */
1206
1214
  EnableCloudwatchLogsExports?: LogTypeList;
1215
+ /**
1216
+ * The DB engine mode of the DB cluster, either provisioned or serverless.
1217
+ */
1218
+ EngineMode?: String;
1219
+ /**
1220
+ * For DB clusters in serverless DB engine mode, the scaling properties of the DB cluster.
1221
+ */
1222
+ ScalingConfiguration?: ScalingConfiguration;
1207
1223
  /**
1208
1224
  * The ID of the region that contains the source for the read replica.
1209
1225
  */
@@ -1341,7 +1357,7 @@ declare namespace RDS {
1341
1357
  */
1342
1358
  CharacterSetName?: String;
1343
1359
  /**
1344
- * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. Default: The default behavior varies depending on whether a VPC has been requested or not. The following list shows the default behavior in each case. Default VPC: true VPC: false If no DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is publicly accessible. If a specific DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is private.
1360
+ * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. Default: The default behavior varies depending on whether DBSubnetGroupName is specified. If DBSubnetGroupName is not specified, and PubliclyAccessible is not specified, the following applies: If the default VPC in the target region doesn’t have an Internet gateway attached to it, the DB instance is private. If the default VPC in the target region has an Internet gateway attached to it, the DB instance is public. If DBSubnetGroupName is specified, and PubliclyAccessible is not specified, the following applies: If the subnets are part of a VPC that doesn’t have an Internet gateway attached to it, the DB instance is private. If the subnets are part of a VPC that has an Internet gateway attached to it, the DB instance is public.
1345
1361
  */
1346
1362
  PubliclyAccessible?: BooleanOptional;
1347
1363
  Tags?: TagList;
@@ -1414,7 +1430,7 @@ declare namespace RDS {
1414
1430
  */
1415
1431
  PerformanceInsightsRetentionPeriod?: IntegerOptional;
1416
1432
  /**
1417
- * The list of log types that need to be enabled for exporting to CloudWatch Logs.
1433
+ * The list of log types that need to be enabled for exporting to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
1418
1434
  */
1419
1435
  EnableCloudwatchLogsExports?: LogTypeList;
1420
1436
  /**
@@ -1460,7 +1476,7 @@ declare namespace RDS {
1460
1476
  */
1461
1477
  OptionGroupName?: String;
1462
1478
  /**
1463
- * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. Default: The default behavior varies depending on whether a VPC has been requested or not. The following list shows the default behavior in each case. Default VPC:true VPC:false If no DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is publicly accessible. If a specific DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is private.
1479
+ * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. For more information, see CreateDBInstance.
1464
1480
  */
1465
1481
  PubliclyAccessible?: BooleanOptional;
1466
1482
  Tags?: TagList;
@@ -1509,7 +1525,7 @@ declare namespace RDS {
1509
1525
  */
1510
1526
  PerformanceInsightsRetentionPeriod?: IntegerOptional;
1511
1527
  /**
1512
- * The list of logs that the new DB instance is to export to CloudWatch Logs.
1528
+ * The list of logs that the new DB instance is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
1513
1529
  */
1514
1530
  EnableCloudwatchLogsExports?: LogTypeList;
1515
1531
  /**
@@ -1801,9 +1817,15 @@ declare namespace RDS {
1801
1817
  */
1802
1818
  BacktrackConsumedChangeRecords?: LongOptional;
1803
1819
  /**
1804
- * A list of log types that this DB cluster is configured to export to CloudWatch Logs.
1820
+ * A list of log types that this DB cluster is configured to export to CloudWatch Logs. Log types vary by DB engine. For information about the log types for each DB engine, see Amazon RDS Database Log Files in the Amazon RDS User Guide.
1805
1821
  */
1806
1822
  EnabledCloudwatchLogsExports?: LogTypeList;
1823
+ Capacity?: IntegerOptional;
1824
+ /**
1825
+ * The DB engine mode of the DB cluster, either provisioned or serverless.
1826
+ */
1827
+ EngineMode?: String;
1828
+ ScalingConfigurationInfo?: ScalingConfigurationInfo;
1807
1829
  }
1808
1830
  export interface DBClusterBacktrack {
1809
1831
  /**
@@ -1842,6 +1864,28 @@ declare namespace RDS {
1842
1864
  */
1843
1865
  DBClusterBacktracks?: DBClusterBacktrackList;
1844
1866
  }
1867
+ export interface DBClusterCapacityInfo {
1868
+ /**
1869
+ * A user-supplied DB cluster identifier. This identifier is the unique key that identifies a DB cluster.
1870
+ */
1871
+ DBClusterIdentifier?: String;
1872
+ /**
1873
+ * A value that specifies the capacity that the DB cluster scales to next.
1874
+ */
1875
+ PendingCapacity?: IntegerOptional;
1876
+ /**
1877
+ * The current capacity of the DB cluster.
1878
+ */
1879
+ CurrentCapacity?: IntegerOptional;
1880
+ /**
1881
+ * The number of seconds before a call to ModifyCurrentDBClusterCapacity times out.
1882
+ */
1883
+ SecondsBeforeTimeout?: IntegerOptional;
1884
+ /**
1885
+ * The timeout action of a call to ModifyCurrentDBClusterCapacity, either ForceApplyCapacityChange or RollbackCapacityChange.
1886
+ */
1887
+ TimeoutAction?: String;
1888
+ }
1845
1889
  export type DBClusterList = DBCluster[];
1846
1890
  export interface DBClusterMember {
1847
1891
  /**
@@ -1937,6 +1981,7 @@ declare namespace RDS {
1937
1981
  * Describes the state of association between the IAM role and the DB cluster. The Status property returns one of the following values: ACTIVE - the IAM role ARN is associated with the DB cluster and can be used to access other AWS services on your behalf. PENDING - the IAM role ARN is being associated with the DB cluster. INVALID - the IAM role ARN is associated with the DB cluster, but the DB cluster is unable to assume the IAM role in order to access other AWS services on your behalf.
1938
1982
  */
1939
1983
  Status?: String;
1984
+ FeatureName?: String;
1940
1985
  }
1941
1986
  export type DBClusterRoles = DBClusterRole[];
1942
1987
  export interface DBClusterSnapshot {
@@ -2102,6 +2147,10 @@ declare namespace RDS {
2102
2147
  * Indicates whether the database engine version supports read replicas.
2103
2148
  */
2104
2149
  SupportsReadReplica?: Boolean;
2150
+ /**
2151
+ * A list of the supported DB engine modes.
2152
+ */
2153
+ SupportedEngineModes?: EngineModeList;
2105
2154
  }
2106
2155
  export type DBEngineVersionList = DBEngineVersion[];
2107
2156
  export interface DBEngineVersionMessage {
@@ -2236,7 +2285,7 @@ declare namespace RDS {
2236
2285
  */
2237
2286
  SecondaryAvailabilityZone?: String;
2238
2287
  /**
2239
- * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. Default: The default behavior varies depending on whether a VPC has been requested or not. The following list shows the default behavior in each case. Default VPC:true VPC:false If no DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is publicly accessible. If a specific DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is private.
2288
+ * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address.
2240
2289
  */
2241
2290
  PubliclyAccessible?: Boolean;
2242
2291
  /**
@@ -2324,7 +2373,7 @@ declare namespace RDS {
2324
2373
  */
2325
2374
  PerformanceInsightsRetentionPeriod?: IntegerOptional;
2326
2375
  /**
2327
- * A list of log types that this DB instance is configured to export to CloudWatch Logs.
2376
+ * A list of log types that this DB instance is configured to export to CloudWatch Logs. Log types vary by DB engine. For information about the log types for each DB engine, see Amazon RDS Database Log Files in the Amazon RDS User Guide.
2328
2377
  */
2329
2378
  EnabledCloudwatchLogsExports?: LogTypeList;
2330
2379
  /**
@@ -2353,7 +2402,7 @@ declare namespace RDS {
2353
2402
  */
2354
2403
  Normal?: Boolean;
2355
2404
  /**
2356
- * Status of the DB instance. For a StatusType of read replica, the values can be replicating, error, stopped, or terminated.
2405
+ * Status of the DB instance. For a StatusType of read replica, the values can be replicating, replication stop point set, replication stop point reached, error, stopped, or terminated.
2357
2406
  */
2358
2407
  Status?: String;
2359
2408
  /**
@@ -3540,6 +3589,7 @@ declare namespace RDS {
3540
3589
  */
3541
3590
  Parameters?: ParametersList;
3542
3591
  }
3592
+ export type EngineModeList = String[];
3543
3593
  export interface Event {
3544
3594
  /**
3545
3595
  * Provides the identifier for the source of the event.
@@ -3700,6 +3750,24 @@ declare namespace RDS {
3700
3750
  export type LogTypeList = String[];
3701
3751
  export type Long = number;
3702
3752
  export type LongOptional = number;
3753
+ export interface ModifyCurrentDBClusterCapacityMessage {
3754
+ /**
3755
+ * The DB cluster identifier for the cluster being modified. This parameter is not case-sensitive. Constraints: Must match the identifier of an existing DB cluster.
3756
+ */
3757
+ DBClusterIdentifier: String;
3758
+ /**
3759
+ * The DB cluster capacity. Constraints: Value must be 2, 4, 8, 16, 32, 64, 128, or 256.
3760
+ */
3761
+ Capacity?: IntegerOptional;
3762
+ /**
3763
+ * The amount of time, in seconds, that Aurora Serverless tries to find a scaling point to perform seamless scaling before enforcing the timeout action. The default is 300. Value must be from 10 through 600.
3764
+ */
3765
+ SecondsBeforeTimeout?: IntegerOptional;
3766
+ /**
3767
+ * The action to take when the timeout is reached, either ForceApplyCapacityChange or RollbackCapacityChange. ForceApplyCapacityChange, the default, sets the capacity to the specified value as soon as possible. RollbackCapacityChange ignores the capacity change if a scaling point is not found in the timeout period.
3768
+ */
3769
+ TimeoutAction?: String;
3770
+ }
3703
3771
  export interface ModifyDBClusterMessage {
3704
3772
  /**
3705
3773
  * The DB cluster identifier for the cluster being modified. This parameter is not case-sensitive. Constraints: Must match the identifier of an existing DBCluster.
@@ -3761,6 +3829,10 @@ declare namespace RDS {
3761
3829
  * The version number of the database engine to which you want to upgrade. Changing this parameter results in an outage. The change is applied during the next maintenance window unless the ApplyImmediately parameter is set to true. For a list of valid engine versions, see CreateDBCluster, or call DescribeDBEngineVersions.
3762
3830
  */
3763
3831
  EngineVersion?: String;
3832
+ /**
3833
+ * The scaling properties of the DB cluster. You can only modify scaling properties for DB clusters in serverless DB engine mode.
3834
+ */
3835
+ ScalingConfiguration?: ScalingConfiguration;
3764
3836
  }
3765
3837
  export interface ModifyDBClusterParameterGroupMessage {
3766
3838
  /**
@@ -4430,6 +4502,10 @@ declare namespace RDS {
4430
4502
  * A list of the available processor features for the DB instance class of a DB instance.
4431
4503
  */
4432
4504
  AvailableProcessorFeatures?: AvailableProcessorFeatureList;
4505
+ /**
4506
+ * A list of the supported DB engine modes.
4507
+ */
4508
+ SupportedEngineModes?: EngineModeList;
4433
4509
  }
4434
4510
  export type OrderableDBInstanceOptionsList = OrderableDBInstanceOption[];
4435
4511
  export interface OrderableDBInstanceOptionsMessage {
@@ -4483,6 +4559,10 @@ declare namespace RDS {
4483
4559
  * Indicates when to apply parameter updates.
4484
4560
  */
4485
4561
  ApplyMethod?: ApplyMethod;
4562
+ /**
4563
+ * The valid DB engine modes.
4564
+ */
4565
+ SupportedEngineModes?: EngineModeList;
4486
4566
  }
4487
4567
  export type ParametersList = Parameter[];
4488
4568
  export interface PendingCloudwatchLogsExports {
@@ -4989,7 +5069,7 @@ declare namespace RDS {
4989
5069
  */
4990
5070
  BacktrackWindow?: LongOptional;
4991
5071
  /**
4992
- * The list of logs that the restored DB cluster is to export to CloudWatch Logs.
5072
+ * The list of logs that the restored DB cluster is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
4993
5073
  */
4994
5074
  EnableCloudwatchLogsExports?: LogTypeList;
4995
5075
  }
@@ -5054,9 +5134,17 @@ declare namespace RDS {
5054
5134
  */
5055
5135
  BacktrackWindow?: LongOptional;
5056
5136
  /**
5057
- * The list of logs that the restored DB cluster is to export to CloudWatch Logs.
5137
+ * The list of logs that the restored DB cluster is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
5058
5138
  */
5059
5139
  EnableCloudwatchLogsExports?: LogTypeList;
5140
+ /**
5141
+ * The DB engine mode of the DB cluster, either provisioned or serverless.
5142
+ */
5143
+ EngineMode?: String;
5144
+ /**
5145
+ * For DB clusters in serverless DB engine mode, the scaling properties of the DB cluster.
5146
+ */
5147
+ ScalingConfiguration?: ScalingConfiguration;
5060
5148
  }
5061
5149
  export interface RestoreDBClusterFromSnapshotResult {
5062
5150
  DBCluster?: DBCluster;
@@ -5112,7 +5200,7 @@ declare namespace RDS {
5112
5200
  */
5113
5201
  BacktrackWindow?: LongOptional;
5114
5202
  /**
5115
- * The list of logs that the restored DB cluster is to export to CloudWatch Logs.
5203
+ * The list of logs that the restored DB cluster is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
5116
5204
  */
5117
5205
  EnableCloudwatchLogsExports?: LogTypeList;
5118
5206
  }
@@ -5149,7 +5237,7 @@ declare namespace RDS {
5149
5237
  */
5150
5238
  MultiAZ?: BooleanOptional;
5151
5239
  /**
5152
- * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. Default: The default behavior varies depending on whether a VPC has been requested or not. The following list shows the default behavior in each case. Default VPC: true VPC: false If no DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is publicly accessible. If a specific DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is private.
5240
+ * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. For more information, see CreateDBInstance.
5153
5241
  */
5154
5242
  PubliclyAccessible?: BooleanOptional;
5155
5243
  /**
@@ -5206,7 +5294,7 @@ declare namespace RDS {
5206
5294
  */
5207
5295
  EnableIAMDatabaseAuthentication?: BooleanOptional;
5208
5296
  /**
5209
- * The list of logs that the restored DB instance is to export to CloudWatch Logs.
5297
+ * The list of logs that the restored DB instance is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
5210
5298
  */
5211
5299
  EnableCloudwatchLogsExports?: LogTypeList;
5212
5300
  /**
@@ -5311,7 +5399,7 @@ declare namespace RDS {
5311
5399
  */
5312
5400
  OptionGroupName?: String;
5313
5401
  /**
5314
- * Specifies whether the DB instance is publicly accessible or not. For more information, see CreateDBInstance.
5402
+ * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. For more information, see CreateDBInstance.
5315
5403
  */
5316
5404
  PubliclyAccessible?: BooleanOptional;
5317
5405
  /**
@@ -5379,7 +5467,7 @@ declare namespace RDS {
5379
5467
  */
5380
5468
  PerformanceInsightsRetentionPeriod?: IntegerOptional;
5381
5469
  /**
5382
- * The list of logs that the restored DB instance is to export to CloudWatch Logs.
5470
+ * The list of logs that the restored DB instance is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
5383
5471
  */
5384
5472
  EnableCloudwatchLogsExports?: LogTypeList;
5385
5473
  /**
@@ -5432,7 +5520,7 @@ declare namespace RDS {
5432
5520
  */
5433
5521
  MultiAZ?: BooleanOptional;
5434
5522
  /**
5435
- * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. Default: The default behavior varies depending on whether a VPC has been requested or not. The following list shows the default behavior in each case. Default VPC:true VPC:false If no DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is publicly accessible. If a specific DB subnet group has been specified as part of the request and the PubliclyAccessible value has not been set, the DB instance is private.
5523
+ * Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. For more information, see CreateDBInstance.
5436
5524
  */
5437
5525
  PubliclyAccessible?: BooleanOptional;
5438
5526
  /**
@@ -5489,7 +5577,7 @@ declare namespace RDS {
5489
5577
  */
5490
5578
  EnableIAMDatabaseAuthentication?: BooleanOptional;
5491
5579
  /**
5492
- * The list of logs that the restored DB instance is to export to CloudWatch Logs.
5580
+ * The list of logs that the restored DB instance is to export to CloudWatch Logs. The values in the list depend on the DB engine being used. For more information, see Publishing Database Logs to Amazon CloudWatch Logs in the Amazon Relational Database Service User Guide.
5493
5581
  */
5494
5582
  EnableCloudwatchLogsExports?: LogTypeList;
5495
5583
  /**
@@ -5529,6 +5617,42 @@ declare namespace RDS {
5529
5617
  export interface RevokeDBSecurityGroupIngressResult {
5530
5618
  DBSecurityGroup?: DBSecurityGroup;
5531
5619
  }
5620
+ export interface ScalingConfiguration {
5621
+ /**
5622
+ * The minimum capacity for an Aurora DB cluster in serverless DB engine mode. Valid capacity values are 2, 4, 8, 16, 32, 64, 128, and 256. The minimum capacity must be less than or equal to the maximum capacity.
5623
+ */
5624
+ MinCapacity?: IntegerOptional;
5625
+ /**
5626
+ * The maximum capacity for an Aurora DB cluster in serverless DB engine mode. Valid capacity values are 2, 4, 8, 16, 32, 64, 128, and 256. The maximum capacity must be greater than or equal to the minimum capacity.
5627
+ */
5628
+ MaxCapacity?: IntegerOptional;
5629
+ /**
5630
+ * A value that specifies whether to allow or disallow automatic pause for an Aurora DB cluster in serverless DB engine mode. A DB cluster can be paused only when it's idle (it has no connections). If a DB cluster is paused for more than seven days, the DB cluster might be backed up with a snapshot. In this case, the DB cluster is restored when there is a request to connect to it.
5631
+ */
5632
+ AutoPause?: BooleanOptional;
5633
+ /**
5634
+ * The time, in seconds, before an Aurora DB cluster in serverless mode is paused.
5635
+ */
5636
+ SecondsUntilAutoPause?: IntegerOptional;
5637
+ }
5638
+ export interface ScalingConfigurationInfo {
5639
+ /**
5640
+ * The maximum capacity for the Aurora DB cluster in serverless DB engine mode.
5641
+ */
5642
+ MinCapacity?: IntegerOptional;
5643
+ /**
5644
+ * The maximum capacity for an Aurora DB cluster in serverless DB engine mode.
5645
+ */
5646
+ MaxCapacity?: IntegerOptional;
5647
+ /**
5648
+ * A value that indicates whether automatic pause is allowed for the Aurora DB cluster in serverless DB engine mode.
5649
+ */
5650
+ AutoPause?: BooleanOptional;
5651
+ /**
5652
+ * The remaining amount of time, in seconds, before the Aurora DB cluster in serverless mode is paused. A DB cluster can be paused only when it's idle (it has no connections).
5653
+ */
5654
+ SecondsUntilAutoPause?: IntegerOptional;
5655
+ }
5532
5656
  export type SourceIdsList = String[];
5533
5657
  export interface SourceRegion {
5534
5658
  /**
@@ -748,7 +748,7 @@ declare namespace SageMaker {
748
748
  */
749
749
  MaxPayloadInMB?: MaxPayloadInMB;
750
750
  /**
751
- * Determines the number of records included in a single mini-batch. SingleRecord means only one record is used per mini-batch. MultiRecord means a mini-batch is set to contain as many records that can fit within the MaxPayloadInMB limit. Batch transform will automatically split your input data into whatever payload size is specified if you set SplitType to Line and BatchStrategy to MultiRecord. There's no need to split the dataset into smaller files or to use larger payload sizes unless the records in your dataset are very large.
751
+ * Determines the number of records included in a single mini-batch. SingleRecord means only one record is used per mini-batch. MultiRecord means a mini-batch is set to contain as many records that can fit within the MaxPayloadInMB limit.
752
752
  */
753
753
  BatchStrategy?: BatchStrategy;
754
754
  /**
@@ -1126,7 +1126,7 @@ declare namespace SageMaker {
1126
1126
  */
1127
1127
  TrainingJobStatus: TrainingJobStatus;
1128
1128
  /**
1129
- * Provides granular information about the system state. For more information, see TrainingJobStatus. Starting - starting the training job. LaunchingMLInstances - launching ML instances for the training job. PreparingTrainingStack - preparing the ML instances for the training job. Downloading - downloading the input data. DownloadingTrainingImage - downloading the training algorithm image. Training - model training is in progress. Uploading - uploading the trained model. Stopping - stopping the training job. Stopped - the training job has stopped. MaxRuntimeExceeded - the training job exceeded the specified max run time and has been stopped. Completed - the training job has completed. Failed - the training job has failed. The failure reason is provided in the StatusMessage. The valid values for SecondaryStatus are subject to change. They primarily provide information on the progress of the training job.
1129
+ * Provides granular information about the system state. For more information, see TrainingJobStatus. Starting - starting the training job. LaunchingMLInstances - launching ML instances for the training job. PreparingTrainingStack - preparing the ML instances for the training job. Downloading - downloading the input data. DownloadingTrainingImage - downloading the training algorithm image. Training - model training is in progress. Uploading - uploading the trained model. Stopping - stopping the training job. Stopped - the training job has stopped. MaxRuntimeExceeded - the training exceed the specified the max run time, which means the training job is stopping. Completed - the training job has completed. Failed - the training job has failed. The failure reason is provided in the StatusMessage. The valid values for SecondaryStatus are subject to change. They primary provide information on the progress of the training job.
1130
1130
  */
1131
1131
  SecondaryStatus: SecondaryStatus;
1132
1132
  /**
@@ -1182,7 +1182,7 @@ declare namespace SageMaker {
1182
1182
  */
1183
1183
  LastModifiedTime?: Timestamp;
1184
1184
  /**
1185
- * To give an overview of the training job lifecycle, SecondaryStatusTransitions is a log of time-ordered secondary statuses that a training job has transitioned.
1185
+ * A log of time-ordered secondary statuses that a training job has transitioned.
1186
1186
  */
1187
1187
  SecondaryStatusTransitions?: SecondaryStatusTransitions;
1188
1188
  }
@@ -2254,7 +2254,7 @@ declare namespace SageMaker {
2254
2254
  */
2255
2255
  StartTime: Timestamp;
2256
2256
  /**
2257
- * A timestamp that shows when the secondary status has ended and the job has transitioned into another secondary status. The EndTime timestamp is also set after the training job has ended.
2257
+ * A timestamp that shows when the secondary status has ended and the job has transitioned into another secondary status.
2258
2258
  */
2259
2259
  EndTime?: Timestamp;
2260
2260
  /**
@@ -140,11 +140,11 @@ declare class SecretsManager extends Service {
140
140
  */
141
141
  untagResource(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
142
142
  /**
143
- * Modifies many of the details of a secret. If you include a ClientRequestToken and either SecretString or SecretBinary then it also creates a new version attached to the secret. To modify the rotation configuration of a secret, use RotateSecret instead. The Secrets Manager console uses only the SecretString parameter and therefore limits you to encrypting and storing only a text string. To encrypt and store binary data as part of the version of a secret, you must use either the AWS CLI or one of the AWS SDKs. If a version with a SecretVersionId with the same value as the ClientRequestToken parameter already exists, the operation generates an error. You cannot modify an existing version, you can only create new ones. If you include SecretString or SecretBinary to create a new secret version, Secrets Manager automatically attaches the staging label AWSCURRENT to the new version. If you call an operation that needs to encrypt or decrypt the SecretString or SecretBinary for a secret in the same account as the calling user and that secret doesn't specify a AWS KMS encryption key, Secrets Manager uses the account's default AWS managed customer master key (CMK) with the alias aws/secretsmanager. If this key doesn't already exist in your account then Secrets Manager creates it for you automatically. All users in the same AWS account automatically have access to use the default CMK. Note that if an Secrets Manager API call results in AWS having to create the account's AWS-managed CMK, it can result in a one-time significant delay in returning the result. If the secret is in a different AWS account from the credentials calling an API that requires encryption or decryption of the secret value then you must create and use a custom AWS KMS CMK because you can't access the default CMK for the account using credentials from a different AWS account. Store the ARN of the CMK in the secret when you create the secret or when you update it by including it in the KMSKeyId. If you call an API that must encrypt or decrypt SecretString or SecretBinary using credentials from a different account then the AWS KMS key policy must grant cross-account access to that other account's user or role for both the kms:GenerateDataKey and kms:Decrypt operations. Minimum permissions To run this command, you must have the following permissions: secretsmanager:UpdateSecret kms:GenerateDataKey - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. kms:Decrypt - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. Related operations To create a new secret, use CreateSecret. To add only a new version to an existing secret, use PutSecretValue. To get the details for a secret, use DescribeSecret. To list the versions contained in a secret, use ListSecretVersionIds.
143
+ * Modifies many of the details of the specified secret. If you include a ClientRequestToken and either SecretString or SecretBinary then it also creates a new version attached to the secret. To modify the rotation configuration of a secret, use RotateSecret instead. The Secrets Manager console uses only the SecretString parameter and therefore limits you to encrypting and storing only a text string. To encrypt and store binary data as part of the version of a secret, you must use either the AWS CLI or one of the AWS SDKs. If a version with a SecretVersionId with the same value as the ClientRequestToken parameter already exists, the operation results in an error. You cannot modify an existing version, you can only create a new version. If you include SecretString or SecretBinary to create a new secret version, Secrets Manager automatically attaches the staging label AWSCURRENT to the new version. If you call an operation that needs to encrypt or decrypt the SecretString or SecretBinary for a secret in the same account as the calling user and that secret doesn't specify a AWS KMS encryption key, Secrets Manager uses the account's default AWS managed customer master key (CMK) with the alias aws/secretsmanager. If this key doesn't already exist in your account then Secrets Manager creates it for you automatically. All users in the same AWS account automatically have access to use the default CMK. Note that if an Secrets Manager API call results in AWS having to create the account's AWS-managed CMK, it can result in a one-time significant delay in returning the result. If the secret is in a different AWS account from the credentials calling an API that requires encryption or decryption of the secret value then you must create and use a custom AWS KMS CMK because you can't access the default CMK for the account using credentials from a different AWS account. Store the ARN of the CMK in the secret when you create the secret or when you update it by including it in the KMSKeyId. If you call an API that must encrypt or decrypt SecretString or SecretBinary using credentials from a different account then the AWS KMS key policy must grant cross-account access to that other account's user or role for both the kms:GenerateDataKey and kms:Decrypt operations. Minimum permissions To run this command, you must have the following permissions: secretsmanager:UpdateSecret kms:GenerateDataKey - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. kms:Decrypt - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. Related operations To create a new secret, use CreateSecret. To add only a new version to an existing secret, use PutSecretValue. To get the details for a secret, use DescribeSecret. To list the versions contained in a secret, use ListSecretVersionIds.
144
144
  */
145
145
  updateSecret(params: SecretsManager.Types.UpdateSecretRequest, callback?: (err: AWSError, data: SecretsManager.Types.UpdateSecretResponse) => void): Request<SecretsManager.Types.UpdateSecretResponse, AWSError>;
146
146
  /**
147
- * Modifies many of the details of a secret. If you include a ClientRequestToken and either SecretString or SecretBinary then it also creates a new version attached to the secret. To modify the rotation configuration of a secret, use RotateSecret instead. The Secrets Manager console uses only the SecretString parameter and therefore limits you to encrypting and storing only a text string. To encrypt and store binary data as part of the version of a secret, you must use either the AWS CLI or one of the AWS SDKs. If a version with a SecretVersionId with the same value as the ClientRequestToken parameter already exists, the operation generates an error. You cannot modify an existing version, you can only create new ones. If you include SecretString or SecretBinary to create a new secret version, Secrets Manager automatically attaches the staging label AWSCURRENT to the new version. If you call an operation that needs to encrypt or decrypt the SecretString or SecretBinary for a secret in the same account as the calling user and that secret doesn't specify a AWS KMS encryption key, Secrets Manager uses the account's default AWS managed customer master key (CMK) with the alias aws/secretsmanager. If this key doesn't already exist in your account then Secrets Manager creates it for you automatically. All users in the same AWS account automatically have access to use the default CMK. Note that if an Secrets Manager API call results in AWS having to create the account's AWS-managed CMK, it can result in a one-time significant delay in returning the result. If the secret is in a different AWS account from the credentials calling an API that requires encryption or decryption of the secret value then you must create and use a custom AWS KMS CMK because you can't access the default CMK for the account using credentials from a different AWS account. Store the ARN of the CMK in the secret when you create the secret or when you update it by including it in the KMSKeyId. If you call an API that must encrypt or decrypt SecretString or SecretBinary using credentials from a different account then the AWS KMS key policy must grant cross-account access to that other account's user or role for both the kms:GenerateDataKey and kms:Decrypt operations. Minimum permissions To run this command, you must have the following permissions: secretsmanager:UpdateSecret kms:GenerateDataKey - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. kms:Decrypt - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. Related operations To create a new secret, use CreateSecret. To add only a new version to an existing secret, use PutSecretValue. To get the details for a secret, use DescribeSecret. To list the versions contained in a secret, use ListSecretVersionIds.
147
+ * Modifies many of the details of the specified secret. If you include a ClientRequestToken and either SecretString or SecretBinary then it also creates a new version attached to the secret. To modify the rotation configuration of a secret, use RotateSecret instead. The Secrets Manager console uses only the SecretString parameter and therefore limits you to encrypting and storing only a text string. To encrypt and store binary data as part of the version of a secret, you must use either the AWS CLI or one of the AWS SDKs. If a version with a SecretVersionId with the same value as the ClientRequestToken parameter already exists, the operation results in an error. You cannot modify an existing version, you can only create a new version. If you include SecretString or SecretBinary to create a new secret version, Secrets Manager automatically attaches the staging label AWSCURRENT to the new version. If you call an operation that needs to encrypt or decrypt the SecretString or SecretBinary for a secret in the same account as the calling user and that secret doesn't specify a AWS KMS encryption key, Secrets Manager uses the account's default AWS managed customer master key (CMK) with the alias aws/secretsmanager. If this key doesn't already exist in your account then Secrets Manager creates it for you automatically. All users in the same AWS account automatically have access to use the default CMK. Note that if an Secrets Manager API call results in AWS having to create the account's AWS-managed CMK, it can result in a one-time significant delay in returning the result. If the secret is in a different AWS account from the credentials calling an API that requires encryption or decryption of the secret value then you must create and use a custom AWS KMS CMK because you can't access the default CMK for the account using credentials from a different AWS account. Store the ARN of the CMK in the secret when you create the secret or when you update it by including it in the KMSKeyId. If you call an API that must encrypt or decrypt SecretString or SecretBinary using credentials from a different account then the AWS KMS key policy must grant cross-account access to that other account's user or role for both the kms:GenerateDataKey and kms:Decrypt operations. Minimum permissions To run this command, you must have the following permissions: secretsmanager:UpdateSecret kms:GenerateDataKey - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. kms:Decrypt - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager. Related operations To create a new secret, use CreateSecret. To add only a new version to an existing secret, use PutSecretValue. To get the details for a secret, use DescribeSecret. To list the versions contained in a secret, use ListSecretVersionIds.
148
148
  */
149
149
  updateSecret(callback?: (err: AWSError, data: SecretsManager.Types.UpdateSecretResponse) => void): Request<SecretsManager.Types.UpdateSecretResponse, AWSError>;
150
150
  /**
@@ -250,6 +250,10 @@ declare namespace SecretsManager {
250
250
  * (Optional) Specifies the number of days that Secrets Manager waits before it can delete the secret. This value can range from 7 to 30 days. The default value is 30.
251
251
  */
252
252
  RecoveryWindowInDays?: RecoveryWindowInDaysType;
253
+ /**
254
+ * (Optional) Specifies that the secret is to be deleted immediately without any recovery window. You cannot use both this parameter and the RecoveryWindowInDays parameter in the same API call. An asynchronous background process performs the actual deletion, so there can be a short delay before the operation completes. If you write code to delete and then immediately recreate a secret with the same name, ensure that your code includes appropriate back off and retry logic. Use this parameter with caution. This parameter causes the operation to skip the normal waiting period before the permanent deletion that AWS would normally impose with the RecoveryWindowInDays parameter. If you delete a secret with the ForceDeleteWithouRecovery parameter, then you have no opportunity to recover the secret. It is permanently lost.
255
+ */
256
+ ForceDeleteWithoutRecovery?: BooleanType;
253
257
  }
254
258
  export interface DeleteSecretResponse {
255
259
  /**
@@ -741,7 +745,7 @@ declare namespace SecretsManager {
741
745
  }
742
746
  export interface UpdateSecretRequest {
743
747
  /**
744
- * Specifies the secret that you want to update or to which you want to add a new version. You can specify either the Amazon Resource Name (ARN) or the friendly name of the secret.
748
+ * Specifies the secret that you want to modify or to which you want to add a new version. You can specify either the Amazon Resource Name (ARN) or the friendly name of the secret.
745
749
  */
746
750
  SecretId: SecretIdType;
747
751
  /**
@@ -749,33 +753,33 @@ declare namespace SecretsManager {
749
753
  */
750
754
  ClientRequestToken?: ClientRequestTokenType;
751
755
  /**
752
- * (Optional) Specifies a user-provided description of the secret.
756
+ * (Optional) Specifies an updated user-provided description of the secret.
753
757
  */
754
758
  Description?: DescriptionType;
755
759
  /**
756
- * (Optional) Specifies the ARN or alias of the AWS KMS customer master key (CMK) to be used to encrypt the protected text in the versions of this secret. If you don't specify this value, then Secrets Manager defaults to using the default CMK in the account (the one named aws/secretsmanager). If a AWS KMS CMK with that name doesn't exist, then Secrets Manager creates it for you automatically the first time it needs to encrypt a version's Plaintext or PlaintextString fields. You can only use the account's default CMK to encrypt and decrypt if you call this operation using credentials from the same account that owns the secret. If the secret is in a different account, then you must create a custom CMK and provide the ARN in this field.
760
+ * (Optional) Specifies an updated ARN or alias of the AWS KMS customer master key (CMK) to be used to encrypt the protected text in new versions of this secret. You can only use the account's default CMK to encrypt and decrypt if you call this operation using credentials from the same account that owns the secret. If the secret is in a different account, then you must create a custom CMK and provide the ARN of that CMK in this field. The user making the call must have permissions to both the secret and the CMK in their respective accounts.
757
761
  */
758
762
  KmsKeyId?: KmsKeyIdType;
759
763
  /**
760
- * (Optional) Specifies binary data that you want to encrypt and store in the new version of the secret. To use this parameter in the command-line tools, we recommend that you store your binary data in a file and then use the appropriate technique for your tool to pass the contents of the file as a parameter. Either SecretBinary or SecretString must have a value, but not both. They cannot both be empty. This parameter is not accessible using the Secrets Manager console.
764
+ * (Optional) Specifies updated binary data that you want to encrypt and store in the new version of the secret. To use this parameter in the command-line tools, we recommend that you store your binary data in a file and then use the appropriate technique for your tool to pass the contents of the file as a parameter. Either SecretBinary or SecretString must have a value, but not both. They cannot both be empty. This parameter is not accessible using the Secrets Manager console.
761
765
  */
762
766
  SecretBinary?: SecretBinaryType;
763
767
  /**
764
- * (Optional) Specifies text data that you want to encrypt and store in this new version of the secret. Either SecretBinary or SecretString must have a value, but not both. They cannot both be empty. If you create this secret by using the Secrets Manager console then Secrets Manager puts the protected secret text in only the SecretString parameter. The Secrets Manager console stores the information as a JSON structure of key/value pairs that the default Lambda rotation function knows how to parse. For storing multiple values, we recommend that you use a JSON text string argument and specify key/value pairs. For information on how to format a JSON parameter for the various command line tool environments, see Using JSON for Parameters in the AWS CLI User Guide. For example: [{"username":"bob"},{"password":"abc123xyz456"}] If your command-line tool or SDK requires quotation marks around the parameter, you should use single quotes to avoid confusion with the double quotes required in the JSON text.
768
+ * (Optional) Specifies updated text data that you want to encrypt and store in this new version of the secret. Either SecretBinary or SecretString must have a value, but not both. They cannot both be empty. If you create this secret by using the Secrets Manager console then Secrets Manager puts the protected secret text in only the SecretString parameter. The Secrets Manager console stores the information as a JSON structure of key/value pairs that the default Lambda rotation function knows how to parse. For storing multiple values, we recommend that you use a JSON text string argument and specify key/value pairs. For information on how to format a JSON parameter for the various command line tool environments, see Using JSON for Parameters in the AWS CLI User Guide. For example: [{"username":"bob"},{"password":"abc123xyz456"}] If your command-line tool or SDK requires quotation marks around the parameter, you should use single quotes to avoid confusion with the double quotes required in the JSON text. You can also 'escape' the double quote character in the embedded JSON text by prefacing each with a backslash. For example, the following string is surrounded by double-quotes. All of the embedded double quotes are escaped: "[{\"username\":\"bob\"},{\"password\":\"abc123xyz456\"}]"
765
769
  */
766
770
  SecretString?: SecretStringType;
767
771
  }
768
772
  export interface UpdateSecretResponse {
769
773
  /**
770
- * The ARN of this secret. Secrets Manager automatically adds several random characters to the name at the end of the ARN when you initially create a secret. This affects only the ARN and not the actual friendly name. This ensures that if you create a new secret with the same name as an old secret that you previously deleted, then users with access to the old secret don't automatically get access to the new secret because the ARNs are different.
774
+ * The ARN of the secret that was updated. Secrets Manager automatically adds several random characters to the name at the end of the ARN when you initially create a secret. This affects only the ARN and not the actual friendly name. This ensures that if you create a new secret with the same name as an old secret that you previously deleted, then users with access to the old secret don't automatically get access to the new secret because the ARNs are different.
771
775
  */
772
776
  ARN?: SecretARNType;
773
777
  /**
774
- * The friendly name of this secret.
778
+ * The friendly name of the secret that was updated.
775
779
  */
776
780
  Name?: SecretNameType;
777
781
  /**
778
- * If a version of the secret was created or updated by this operation, then its unique identifier is returned.
782
+ * If a new version of the secret was created by this operation, then VersionId contains the unique identifier of the new version.
779
783
  */
780
784
  VersionId?: SecretVersionIdType;
781
785
  }
@@ -793,7 +797,7 @@ declare namespace SecretsManager {
793
797
  */
794
798
  RemoveFromVersionId?: SecretVersionIdType;
795
799
  /**
796
- * (Optional) The secret version ID that you want to add the staging labels to. If any of the staging labels are already attached to a different version of the secret, then they are removed from that version before adding them to this version.
800
+ * (Optional) The secret version ID that you want to add the staging labels to. If any of the staging labels are already attached to a different version of the secret, then they are automatically removed from that version before adding them to this version.
797
801
  */
798
802
  MoveToVersionId?: SecretVersionIdType;
799
803
  }
package/clients/ssm.d.ts CHANGED
@@ -1289,6 +1289,10 @@ declare namespace SSM {
1289
1289
  * The specified targets.
1290
1290
  */
1291
1291
  Targets?: Targets;
1292
+ /**
1293
+ * The specified key-value mapping of document parameters to target resources.
1294
+ */
1295
+ TargetMaps?: TargetMaps;
1292
1296
  /**
1293
1297
  * A list of resolved targets in the rate control execution.
1294
1298
  */
@@ -1386,6 +1390,10 @@ declare namespace SSM {
1386
1390
  * The targets defined by the user when starting the Automation.
1387
1391
  */
1388
1392
  Targets?: Targets;
1393
+ /**
1394
+ * The specified key-value mapping of document parameters to target resources.
1395
+ */
1396
+ TargetMaps?: TargetMaps;
1389
1397
  /**
1390
1398
  * A list of targets that resolved during the execution.
1391
1399
  */
@@ -1539,11 +1547,11 @@ declare namespace SSM {
1539
1547
  */
1540
1548
  key: CommandFilterKey;
1541
1549
  /**
1542
- * The filter value. Valid values for each filter key are as follows: InvokedAfter: Specify a timestamp to limit your results. For example, specify 2018-07-07T00:00:00Z to see a list of command executions occurring July 7, 2018, and later. InvokedBefore: Specify a timestamp to limit your results. For example, specify 2018-07-07T00:00:00Z to see a list of command executions from before July 7, 2018. Status: Specify a valid command status to see a list of all command executions with that status. Status values you can specify include: Pending InProgress Success Cancelled Failed TimedOut Cancelling DocumentName: Specify name of the SSM document for which you want to see command execution results. For example, specify AWS-RunPatchBaseline to see command executions that used this SSM document to perform security patching operations on instances. ExecutionStage: Specify one of the following values: Executing: Returns a list of command executions that are currently still running. Complete: Returns a list of command exeuctions that have already completed.
1550
+ * The filter value.
1543
1551
  */
1544
1552
  value: CommandFilterValue;
1545
1553
  }
1546
- export type CommandFilterKey = "InvokedAfter"|"InvokedBefore"|"Status"|"ExecutionStage"|"DocumentName"|string;
1554
+ export type CommandFilterKey = "InvokedAfter"|"InvokedBefore"|"Status"|string;
1547
1555
  export type CommandFilterList = CommandFilter[];
1548
1556
  export type CommandFilterValue = string;
1549
1557
  export type CommandId = string;
@@ -5787,7 +5795,7 @@ declare namespace SSM {
5787
5795
  */
5788
5796
  TaskArn: MaintenanceWindowTaskArn;
5789
5797
  /**
5790
- * The role that should be assumed when executing the task.
5798
+ * The role to assume when running the Maintenance Window task. If you do not specify a service role ARN, Systems Manager will use your account's service-linked role for Systems Manager by default. If no service-linked role for Systems Manager exists in your account, it will be created when you run RegisterTaskWithMaintenanceWindow without specifying a service role ARN. For more information, see Service-Linked Role Permissions for Systems Manager and Should I Use a Service-Linked Role or a Custom Service Role to Run Maintenance Window Tasks? in the AWS Systems Manager User Guide.
5791
5799
  */
5792
5800
  ServiceRoleArn?: ServiceRole;
5793
5801
  /**
@@ -6159,6 +6167,10 @@ declare namespace SSM {
6159
6167
  * A key-value mapping to target resources. Required if you specify TargetParameterName.
6160
6168
  */
6161
6169
  Targets?: Targets;
6170
+ /**
6171
+ * A key-value mapping of document parameters to target resources. Both Targets and TargetMaps cannot be specified together.
6172
+ */
6173
+ TargetMaps?: TargetMaps;
6162
6174
  /**
6163
6175
  * The maximum number of targets allowed to run this task in parallel. You can specify a number, such as 10, or a percentage, such as 10%. The default value is 10.
6164
6176
  */
@@ -6316,6 +6328,11 @@ declare namespace SSM {
6316
6328
  }
6317
6329
  export type TargetCount = number;
6318
6330
  export type TargetKey = string;
6331
+ export type TargetMap = {[key: string]: TargetMapValueList};
6332
+ export type TargetMapKey = string;
6333
+ export type TargetMapValue = string;
6334
+ export type TargetMapValueList = TargetMapValue[];
6335
+ export type TargetMaps = TargetMap[];
6319
6336
  export type TargetParameterList = ParameterValue[];
6320
6337
  export type TargetType = string;
6321
6338
  export type TargetValue = string;
@@ -6577,7 +6594,7 @@ declare namespace SSM {
6577
6594
  */
6578
6595
  TaskArn?: MaintenanceWindowTaskArn;
6579
6596
  /**
6580
- * The IAM service role ARN to modify. The system assumes this role during task execution.
6597
+ * The IAM service role ARN to modify. The system assumes this role during task execution. If you do not specify a service role ARN, Systems Manager will use your account's service-linked role for Systems Manager by default. If no service-linked role for Systems Manager exists in your account, it will be created when you run RegisterTaskWithMaintenanceWindow without specifying a service role ARN. For more information, see Service-Linked Role Permissions for Systems Manager and Should I Use a Service-Linked Role or a Custom Service Role to Run Maintenance Window Tasks? in the AWS Systems Manager User Guide.
6581
6598
  */
6582
6599
  ServiceRoleArn?: ServiceRole;
6583
6600
  /**
@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
83
83
  /**
84
84
  * @constant
85
85
  */
86
- VERSION: '2.288.0',
86
+ VERSION: '2.292.0',
87
87
 
88
88
  /**
89
89
  * @api private