aws-sdk 2.1625.0 → 2.1627.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.
@@ -163,6 +163,30 @@ declare class Chatbot extends Service {
163
163
  * Lists all Microsoft Teams user identities with a mapped role.
164
164
  */
165
165
  listMicrosoftTeamsUserIdentities(callback?: (err: AWSError, data: Chatbot.Types.ListMicrosoftTeamsUserIdentitiesResult) => void): Request<Chatbot.Types.ListMicrosoftTeamsUserIdentitiesResult, AWSError>;
166
+ /**
167
+ * Retrieves the list of tags applied to a configuration.
168
+ */
169
+ listTagsForResource(params: Chatbot.Types.ListTagsForResourceRequest, callback?: (err: AWSError, data: Chatbot.Types.ListTagsForResourceResponse) => void): Request<Chatbot.Types.ListTagsForResourceResponse, AWSError>;
170
+ /**
171
+ * Retrieves the list of tags applied to a configuration.
172
+ */
173
+ listTagsForResource(callback?: (err: AWSError, data: Chatbot.Types.ListTagsForResourceResponse) => void): Request<Chatbot.Types.ListTagsForResourceResponse, AWSError>;
174
+ /**
175
+ * Applies the supplied tags to a configuration.
176
+ */
177
+ tagResource(params: Chatbot.Types.TagResourceRequest, callback?: (err: AWSError, data: Chatbot.Types.TagResourceResponse) => void): Request<Chatbot.Types.TagResourceResponse, AWSError>;
178
+ /**
179
+ * Applies the supplied tags to a configuration.
180
+ */
181
+ tagResource(callback?: (err: AWSError, data: Chatbot.Types.TagResourceResponse) => void): Request<Chatbot.Types.TagResourceResponse, AWSError>;
182
+ /**
183
+ * Removes the supplied tags from a configuration
184
+ */
185
+ untagResource(params: Chatbot.Types.UntagResourceRequest, callback?: (err: AWSError, data: Chatbot.Types.UntagResourceResponse) => void): Request<Chatbot.Types.UntagResourceResponse, AWSError>;
186
+ /**
187
+ * Removes the supplied tags from a configuration
188
+ */
189
+ untagResource(callback?: (err: AWSError, data: Chatbot.Types.UntagResourceResponse) => void): Request<Chatbot.Types.UntagResourceResponse, AWSError>;
166
190
  /**
167
191
  * Update Chatbot account level preferences
168
192
  */
@@ -207,6 +231,7 @@ declare namespace Chatbot {
207
231
  */
208
232
  TrainingDataCollectionEnabled?: BooleanAccountPreference;
209
233
  }
234
+ export type AmazonResourceName = string;
210
235
  export type Arn = string;
211
236
  export type AwsUserIdentity = string;
212
237
  export type BooleanAccountPreference = boolean;
@@ -236,6 +261,10 @@ declare namespace Chatbot {
236
261
  * Specifies the logging level for this configuration. This property affects the log entries pushed to Amazon CloudWatch Logs.Logging levels include ERROR, INFO, or NONE.
237
262
  */
238
263
  LoggingLevel?: CustomerCwLogLevel;
264
+ /**
265
+ * A list of tags applied to the configuration.
266
+ */
267
+ Tags?: Tags;
239
268
  }
240
269
  export type ChimeWebhookConfigurationList = ChimeWebhookConfiguration[];
241
270
  export type ChimeWebhookDescription = string;
@@ -281,6 +310,10 @@ declare namespace Chatbot {
281
310
  * Logging levels include ERROR, INFO, or NONE.
282
311
  */
283
312
  LoggingLevel?: CustomerCwLogLevel;
313
+ /**
314
+ * A list of tags to apply to the configuration.
315
+ */
316
+ Tags?: Tags;
284
317
  }
285
318
  export interface CreateChimeWebhookConfigurationResult {
286
319
  /**
@@ -325,6 +358,10 @@ declare namespace Chatbot {
325
358
  * Enables use of a user role requirement in your chat configuration.
326
359
  */
327
360
  UserAuthorizationRequired?: BooleanAccountPreference;
361
+ /**
362
+ * A list of tags to apply to the configuration.
363
+ */
364
+ Tags?: Tags;
328
365
  }
329
366
  export interface CreateSlackChannelConfigurationResult {
330
367
  /**
@@ -377,6 +414,10 @@ declare namespace Chatbot {
377
414
  * Enables use of a user role requirement in your chat configuration.
378
415
  */
379
416
  UserAuthorizationRequired?: BooleanAccountPreference;
417
+ /**
418
+ * A list of tags to apply to the configuration.
419
+ */
420
+ Tags?: Tags;
380
421
  }
381
422
  export interface CreateTeamsChannelConfigurationResult {
382
423
  /**
@@ -611,6 +652,18 @@ declare namespace Chatbot {
611
652
  */
612
653
  NextToken?: PaginationToken;
613
654
  }
655
+ export interface ListTagsForResourceRequest {
656
+ /**
657
+ * The ARN of the configuration.
658
+ */
659
+ ResourceARN: AmazonResourceName;
660
+ }
661
+ export interface ListTagsForResourceResponse {
662
+ /**
663
+ * A list of tags applied to the configuration.
664
+ */
665
+ Tags?: TagList;
666
+ }
614
667
  export interface ListTeamsChannelConfigurationsRequest {
615
668
  /**
616
669
  * The maximum number of results to include in the response. If more results exist than the specified MaxResults value, a token is included in the response so that the remaining results can be retrieved.
@@ -682,6 +735,10 @@ declare namespace Chatbot {
682
735
  * Enables use of a user role requirement in your chat configuration.
683
736
  */
684
737
  UserAuthorizationRequired?: BooleanAccountPreference;
738
+ /**
739
+ * A list of tags applied to the configuration.
740
+ */
741
+ Tags?: Tags;
685
742
  }
686
743
  export type SlackChannelConfigurationList = SlackChannelConfiguration[];
687
744
  export type SlackChannelDisplayName = string;
@@ -725,6 +782,33 @@ declare namespace Chatbot {
725
782
  export type SlackWorkspacesList = SlackWorkspace[];
726
783
  export type SnsTopicArnList = Arn[];
727
784
  export type String = string;
785
+ export interface Tag {
786
+ /**
787
+ * The tag key.
788
+ */
789
+ TagKey: TagKey;
790
+ /**
791
+ * The tag value.
792
+ */
793
+ TagValue: TagValue;
794
+ }
795
+ export type TagKey = string;
796
+ export type TagKeyList = TagKey[];
797
+ export type TagList = Tag[];
798
+ export interface TagResourceRequest {
799
+ /**
800
+ * The ARN of the configuration.
801
+ */
802
+ ResourceARN: AmazonResourceName;
803
+ /**
804
+ * A list of tags to apply to the configuration.
805
+ */
806
+ Tags: TagList;
807
+ }
808
+ export interface TagResourceResponse {
809
+ }
810
+ export type TagValue = string;
811
+ export type Tags = Tag[];
728
812
  export type TeamChannelConfigurationsList = TeamsChannelConfiguration[];
729
813
  export type TeamName = string;
730
814
  export interface TeamsChannelConfiguration {
@@ -776,6 +860,10 @@ declare namespace Chatbot {
776
860
  * Enables use of a user role requirement in your chat configuration.
777
861
  */
778
862
  UserAuthorizationRequired?: BooleanAccountPreference;
863
+ /**
864
+ * A list of tags applied to the configuration.
865
+ */
866
+ Tags?: Tags;
779
867
  }
780
868
  export type TeamsChannelId = string;
781
869
  export type TeamsChannelName = string;
@@ -811,6 +899,18 @@ declare namespace Chatbot {
811
899
  TeamsTenantId?: UUID;
812
900
  }
813
901
  export type UUID = string;
902
+ export interface UntagResourceRequest {
903
+ /**
904
+ * The ARN of the configuration.
905
+ */
906
+ ResourceARN: AmazonResourceName;
907
+ /**
908
+ * A list of tag keys to remove from the configuration.
909
+ */
910
+ TagKeys: TagKeyList;
911
+ }
912
+ export interface UntagResourceResponse {
913
+ }
814
914
  export interface UpdateAccountPreferencesRequest {
815
915
  /**
816
916
  * Enables use of a user role requirement in your chat configuration.
@@ -1399,6 +1399,10 @@ declare namespace CloudFormation {
1399
1399
  * A unique identifier for this DeleteStack request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to delete a stack with the same name. You might retry DeleteStack requests to ensure that CloudFormation successfully received them. All events initiated by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack operation with the token token1, then all the StackEvents generated by that operation will have ClientRequestToken set as token1. In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002.
1400
1400
  */
1401
1401
  ClientRequestToken?: ClientRequestToken;
1402
+ /**
1403
+ * Specifies the deletion mode for the stack. Possible values are: STANDARD - Use the standard behavior. Specifying this value is the same as not specifying this parameter. FORCE_DELETE_STACK - Delete the stack if it's stuck in a DELETE_FAILED state due to resource deletion failure.
1404
+ */
1405
+ DeletionMode?: DeletionMode;
1402
1406
  }
1403
1407
  export interface DeleteStackInstancesInput {
1404
1408
  /**
@@ -1452,6 +1456,7 @@ declare namespace CloudFormation {
1452
1456
  }
1453
1457
  export interface DeleteStackSetOutput {
1454
1458
  }
1459
+ export type DeletionMode = "STANDARD"|"FORCE_DELETE_STACK"|string;
1455
1460
  export type DeletionTime = Date;
1456
1461
  export interface DeploymentTargets {
1457
1462
  /**
@@ -2680,7 +2685,7 @@ declare namespace CloudFormation {
2680
2685
  }
2681
2686
  export interface ListStackInstanceResourceDriftsOutput {
2682
2687
  /**
2683
- * A list of StackInstanceResourceDriftSummary structures that contain information about the specified stack instances.
2688
+ * A list of StackInstanceResourceDriftsSummary structures that contain information about the specified stack instances.
2684
2689
  */
2685
2690
  Summaries?: StackInstanceResourceDriftsSummaries;
2686
2691
  /**
@@ -3806,6 +3811,10 @@ declare namespace CloudFormation {
3806
3811
  * When set to true, newly created resources are deleted when the operation rolls back. This includes newly created resources marked with a deletion policy of Retain. Default: false
3807
3812
  */
3808
3813
  RetainExceptOnCreate?: RetainExceptOnCreate;
3814
+ /**
3815
+ * Specifies the deletion mode for the stack. Possible values are: STANDARD - Use the standard behavior. Specifying this value is the same as not specifying this parameter. FORCE_DELETE_STACK - Delete the stack if it's stuck in a DELETE_FAILED state due to resource deletion failure.
3816
+ */
3817
+ DeletionMode?: DeletionMode;
3809
3818
  /**
3810
3819
  * The detailed status of the resource or stack. If CONFIGURATION_COMPLETE is present, the resource or resource configuration phase has completed and the stabilization of the resources is in progress. The stack sets CONFIGURATION_COMPLETE when all of the resources in the stack have reached that event. For more information, see CloudFormation stack deployment in the CloudFormation User Guide.
3811
3820
  */
@@ -4475,7 +4484,7 @@ declare namespace CloudFormation {
4475
4484
  */
4476
4485
  MaxConcurrentPercentage?: MaxConcurrentPercentage;
4477
4486
  /**
4478
- * Specifies how the concurrency level behaves during the operation execution. STRICT_FAILURE_TOLERANCE: This option dynamically lowers the concurrency level to ensure the number of failed accounts never exceeds the value of FailureToleranceCount +1. The initial actual concurrency is set to the lower of either the value of the MaxConcurrentCount, or the value of MaxConcurrentCount +1. The actual concurrency is then reduced proportionally by the number of failures. This is the default behavior. If failure tolerance or Maximum concurrent accounts are set to percentages, the behavior is similar. SOFT_FAILURE_TOLERANCE: This option decouples FailureToleranceCount from the actual concurrency. This allows stack set operations to run at the concurrency level set by the MaxConcurrentCount value, or MaxConcurrentPercentage, regardless of the number of failures.
4487
+ * Specifies how the concurrency level behaves during the operation execution. STRICT_FAILURE_TOLERANCE: This option dynamically lowers the concurrency level to ensure the number of failed accounts never exceeds the value of FailureToleranceCount +1. The initial actual concurrency is set to the lower of either the value of the MaxConcurrentCount, or the value of FailureToleranceCount +1. The actual concurrency is then reduced proportionally by the number of failures. This is the default behavior. If failure tolerance or Maximum concurrent accounts are set to percentages, the behavior is similar. SOFT_FAILURE_TOLERANCE: This option decouples FailureToleranceCount from the actual concurrency. This allows stack set operations to run at the concurrency level set by the MaxConcurrentCount value, or MaxConcurrentPercentage, regardless of the number of failures.
4479
4488
  */
4480
4489
  ConcurrencyMode?: ConcurrencyMode;
4481
4490
  }
@@ -211,6 +211,10 @@ declare namespace EMRServerless {
211
211
  */
212
212
  runtimeConfiguration?: ConfigurationList;
213
213
  monitoringConfiguration?: MonitoringConfiguration;
214
+ /**
215
+ * The interactive configuration object that enables the interactive use cases for an application.
216
+ */
217
+ interactiveConfiguration?: InteractiveConfiguration;
214
218
  }
215
219
  export type ApplicationArn = string;
216
220
  export type ApplicationId = string;
@@ -411,6 +415,10 @@ declare namespace EMRServerless {
411
415
  * The configuration setting for monitoring.
412
416
  */
413
417
  monitoringConfiguration?: MonitoringConfiguration;
418
+ /**
419
+ * The interactive configuration object that enables the interactive use cases to use when running an application.
420
+ */
421
+ interactiveConfiguration?: InteractiveConfiguration;
414
422
  }
415
423
  export interface CreateApplicationResponse {
416
424
  /**
@@ -535,6 +543,16 @@ declare namespace EMRServerless {
535
543
  }
536
544
  export type InitialCapacityConfigMap = {[key: string]: InitialCapacityConfig};
537
545
  export type Integer = number;
546
+ export interface InteractiveConfiguration {
547
+ /**
548
+ * Enables you to connect an application to Amazon EMR Studio to run interactive workloads in a notebook.
549
+ */
550
+ studioEnabled?: Boolean;
551
+ /**
552
+ * Enables an Apache Livy endpoint that you can connect to and run interactive jobs.
553
+ */
554
+ livyEndpointEnabled?: Boolean;
555
+ }
538
556
  export type JobArn = string;
539
557
  export interface JobDriver {
540
558
  /**
@@ -1010,6 +1028,10 @@ declare namespace EMRServerless {
1010
1028
  * The key-value pairs that specify worker type to WorkerTypeSpecificationInput. This parameter must contain all valid worker types for a Spark or Hive application. Valid worker types include Driver and Executor for Spark applications and HiveDriver and TezTask for Hive applications. You can either set image details in this parameter for each worker type, or in imageConfiguration for all worker types.
1011
1029
  */
1012
1030
  workerTypeSpecifications?: WorkerTypeSpecificationInputMap;
1031
+ /**
1032
+ * The interactive configuration object that contains new interactive use cases when the application is updated.
1033
+ */
1034
+ interactiveConfiguration?: InteractiveConfiguration;
1013
1035
  /**
1014
1036
  * The Amazon EMR release label for the application. You can change the release label to use a different release of Amazon EMR.
1015
1037
  */
package/clients/kms.d.ts CHANGED
@@ -220,11 +220,11 @@ declare class KMS extends Service {
220
220
  */
221
221
  getKeyRotationStatus(callback?: (err: AWSError, data: KMS.Types.GetKeyRotationStatusResponse) => void): Request<KMS.Types.GetKeyRotationStatusResponse, AWSError>;
222
222
  /**
223
- * Returns the public key and an import token you need to import or reimport key material for a KMS key. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. Before calling GetParametersForImport, use the CreateKey operation with an Origin value of EXTERNAL to create a KMS key with no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. You can also use GetParametersForImport to get a public key and import token to reimport the original key material into a KMS key whose key material expired or was deleted. GetParametersForImport returns the items that you need to import your key material. The public key (or "wrapping key") of an RSA key pair that KMS generates. You will use this public key to encrypt ("wrap") your key material while it's in transit to KMS. A import token that ensures that KMS can decrypt your key material and associate it with the correct KMS key. The public key and its import token are permanently linked and must be used together. Each public key and import token set is valid for 24 hours. The expiration date and time appear in the ParametersValidTo field in the GetParametersForImport response. You cannot use an expired public key or import token in an ImportKeyMaterial request. If your key and token expire, send another GetParametersForImport request. GetParametersForImport requires the following information: The key ID of the KMS key for which you are importing the key material. The key spec of the public key ("wrapping key") that you will use to encrypt your key material during import. The wrapping algorithm that you will use with the public key to encrypt your key material. You can use the same or a different public key spec and wrapping algorithm each time you import or reimport the same key material. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:GetParametersForImport (key policy) Related operations: ImportKeyMaterial DeleteImportedKeyMaterial Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
223
+ * Returns the public key and an import token you need to import or reimport key material for a KMS key. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. Before calling GetParametersForImport, use the CreateKey operation with an Origin value of EXTERNAL to create a KMS key with no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. You can also use GetParametersForImport to get a public key and import token to reimport the original key material into a KMS key whose key material expired or was deleted. GetParametersForImport returns the items that you need to import your key material. The public key (or "wrapping key") of an asymmetric key pair that KMS generates. You will use this public key to encrypt ("wrap") your key material while it's in transit to KMS. A import token that ensures that KMS can decrypt your key material and associate it with the correct KMS key. The public key and its import token are permanently linked and must be used together. Each public key and import token set is valid for 24 hours. The expiration date and time appear in the ParametersValidTo field in the GetParametersForImport response. You cannot use an expired public key or import token in an ImportKeyMaterial request. If your key and token expire, send another GetParametersForImport request. GetParametersForImport requires the following information: The key ID of the KMS key for which you are importing the key material. The key spec of the public key ("wrapping key") that you will use to encrypt your key material during import. The wrapping algorithm that you will use with the public key to encrypt your key material. You can use the same or a different public key spec and wrapping algorithm each time you import or reimport the same key material. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:GetParametersForImport (key policy) Related operations: ImportKeyMaterial DeleteImportedKeyMaterial Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
224
224
  */
225
225
  getParametersForImport(params: KMS.Types.GetParametersForImportRequest, callback?: (err: AWSError, data: KMS.Types.GetParametersForImportResponse) => void): Request<KMS.Types.GetParametersForImportResponse, AWSError>;
226
226
  /**
227
- * Returns the public key and an import token you need to import or reimport key material for a KMS key. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. Before calling GetParametersForImport, use the CreateKey operation with an Origin value of EXTERNAL to create a KMS key with no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. You can also use GetParametersForImport to get a public key and import token to reimport the original key material into a KMS key whose key material expired or was deleted. GetParametersForImport returns the items that you need to import your key material. The public key (or "wrapping key") of an RSA key pair that KMS generates. You will use this public key to encrypt ("wrap") your key material while it's in transit to KMS. A import token that ensures that KMS can decrypt your key material and associate it with the correct KMS key. The public key and its import token are permanently linked and must be used together. Each public key and import token set is valid for 24 hours. The expiration date and time appear in the ParametersValidTo field in the GetParametersForImport response. You cannot use an expired public key or import token in an ImportKeyMaterial request. If your key and token expire, send another GetParametersForImport request. GetParametersForImport requires the following information: The key ID of the KMS key for which you are importing the key material. The key spec of the public key ("wrapping key") that you will use to encrypt your key material during import. The wrapping algorithm that you will use with the public key to encrypt your key material. You can use the same or a different public key spec and wrapping algorithm each time you import or reimport the same key material. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:GetParametersForImport (key policy) Related operations: ImportKeyMaterial DeleteImportedKeyMaterial Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
227
+ * Returns the public key and an import token you need to import or reimport key material for a KMS key. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. Before calling GetParametersForImport, use the CreateKey operation with an Origin value of EXTERNAL to create a KMS key with no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. You can also use GetParametersForImport to get a public key and import token to reimport the original key material into a KMS key whose key material expired or was deleted. GetParametersForImport returns the items that you need to import your key material. The public key (or "wrapping key") of an asymmetric key pair that KMS generates. You will use this public key to encrypt ("wrap") your key material while it's in transit to KMS. A import token that ensures that KMS can decrypt your key material and associate it with the correct KMS key. The public key and its import token are permanently linked and must be used together. Each public key and import token set is valid for 24 hours. The expiration date and time appear in the ParametersValidTo field in the GetParametersForImport response. You cannot use an expired public key or import token in an ImportKeyMaterial request. If your key and token expire, send another GetParametersForImport request. GetParametersForImport requires the following information: The key ID of the KMS key for which you are importing the key material. The key spec of the public key ("wrapping key") that you will use to encrypt your key material during import. The wrapping algorithm that you will use with the public key to encrypt your key material. You can use the same or a different public key spec and wrapping algorithm each time you import or reimport the same key material. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:GetParametersForImport (key policy) Related operations: ImportKeyMaterial DeleteImportedKeyMaterial Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
228
228
  */
229
229
  getParametersForImport(callback?: (err: AWSError, data: KMS.Types.GetParametersForImportResponse) => void): Request<KMS.Types.GetParametersForImportResponse, AWSError>;
230
230
  /**
@@ -430,7 +430,7 @@ declare class KMS extends Service {
430
430
  }
431
431
  declare namespace KMS {
432
432
  export type AWSAccountIdType = string;
433
- export type AlgorithmSpec = "RSAES_PKCS1_V1_5"|"RSAES_OAEP_SHA_1"|"RSAES_OAEP_SHA_256"|"RSA_AES_KEY_WRAP_SHA_1"|"RSA_AES_KEY_WRAP_SHA_256"|string;
433
+ export type AlgorithmSpec = "RSAES_PKCS1_V1_5"|"RSAES_OAEP_SHA_1"|"RSAES_OAEP_SHA_256"|"RSA_AES_KEY_WRAP_SHA_1"|"RSA_AES_KEY_WRAP_SHA_256"|"SM2PKE"|string;
434
434
  export type AliasList = AliasListEntry[];
435
435
  export interface AliasListEntry {
436
436
  /**
@@ -1171,11 +1171,11 @@ declare namespace KMS {
1171
1171
  */
1172
1172
  KeyId: KeyIdType;
1173
1173
  /**
1174
- * The algorithm you will use with the RSA public key (PublicKey) in the response to protect your key material during import. For more information, see Select a wrapping algorithm in the Key Management Service Developer Guide. For RSA_AES wrapping algorithms, you encrypt your key material with an AES key that you generate, then encrypt your AES key with the RSA public key from KMS. For RSAES wrapping algorithms, you encrypt your key material directly with the RSA public key from KMS. The wrapping algorithms that you can use depend on the type of key material that you are importing. To import an RSA private key, you must use an RSA_AES wrapping algorithm. RSA_AES_KEY_WRAP_SHA_256 — Supported for wrapping RSA and ECC key material. RSA_AES_KEY_WRAP_SHA_1 — Supported for wrapping RSA and ECC key material. RSAES_OAEP_SHA_256 — Supported for all types of key material, except RSA key material (private key). You cannot use the RSAES_OAEP_SHA_256 wrapping algorithm with the RSA_2048 wrapping key spec to wrap ECC_NIST_P521 key material. RSAES_OAEP_SHA_1 — Supported for all types of key material, except RSA key material (private key). You cannot use the RSAES_OAEP_SHA_1 wrapping algorithm with the RSA_2048 wrapping key spec to wrap ECC_NIST_P521 key material. RSAES_PKCS1_V1_5 (Deprecated) — As of October 10, 2023, KMS does not support the RSAES_PKCS1_V1_5 wrapping algorithm.
1174
+ * The algorithm you will use with the asymmetric public key (PublicKey) in the response to protect your key material during import. For more information, see Select a wrapping algorithm in the Key Management Service Developer Guide. For RSA_AES wrapping algorithms, you encrypt your key material with an AES key that you generate, then encrypt your AES key with the RSA public key from KMS. For RSAES wrapping algorithms, you encrypt your key material directly with the RSA public key from KMS. For SM2PKE wrapping algorithms, you encrypt your key material directly with the SM2 public key from KMS. The wrapping algorithms that you can use depend on the type of key material that you are importing. To import an RSA private key, you must use an RSA_AES wrapping algorithm, except in China Regions, where you must use the SM2PKE wrapping algorithm to import an RSA private key. The SM2PKE wrapping algorithm is available only in China Regions. The RSA_AES_KEY_WRAP_SHA_256 and RSA_AES_KEY_WRAP_SHA_1 wrapping algorithms are not supported in China Regions. RSA_AES_KEY_WRAP_SHA_256 — Supported for wrapping RSA and ECC key material. RSA_AES_KEY_WRAP_SHA_1 — Supported for wrapping RSA and ECC key material. RSAES_OAEP_SHA_256 — Supported for all types of key material, except RSA key material (private key). You cannot use the RSAES_OAEP_SHA_256 wrapping algorithm with the RSA_2048 wrapping key spec to wrap ECC_NIST_P521 key material. RSAES_OAEP_SHA_1 — Supported for all types of key material, except RSA key material (private key). You cannot use the RSAES_OAEP_SHA_1 wrapping algorithm with the RSA_2048 wrapping key spec to wrap ECC_NIST_P521 key material. RSAES_PKCS1_V1_5 (Deprecated) — As of October 10, 2023, KMS does not support the RSAES_PKCS1_V1_5 wrapping algorithm. SM2PKE (China Regions only) — supported for wrapping RSA, ECC, and SM2 key material.
1175
1175
  */
1176
1176
  WrappingAlgorithm: AlgorithmSpec;
1177
1177
  /**
1178
- * The type of RSA public key to return in the response. You will use this wrapping key with the specified wrapping algorithm to protect your key material during import. Use the longest RSA wrapping key that is practical. You cannot use an RSA_2048 public key to directly wrap an ECC_NIST_P521 private key. Instead, use an RSA_AES wrapping algorithm or choose a longer RSA public key.
1178
+ * The type of public key to return in the response. You will use this wrapping key with the specified wrapping algorithm to protect your key material during import. Use the longest wrapping key that is practical. You cannot use an RSA_2048 public key to directly wrap an ECC_NIST_P521 private key. Instead, use an RSA_AES wrapping algorithm or choose a longer RSA public key. The SM2 wrapping key spec is available only in China Regions.
1179
1179
  */
1180
1180
  WrappingKeySpec: WrappingKeySpec;
1181
1181
  }
@@ -2108,7 +2108,7 @@ declare namespace KMS {
2108
2108
  */
2109
2109
  SigningAlgorithm?: SigningAlgorithmSpec;
2110
2110
  }
2111
- export type WrappingKeySpec = "RSA_2048"|"RSA_3072"|"RSA_4096"|string;
2111
+ export type WrappingKeySpec = "RSA_2048"|"RSA_3072"|"RSA_4096"|"SM2"|string;
2112
2112
  export interface XksKeyConfigurationType {
2113
2113
  /**
2114
2114
  * The ID of the external key in its external key manager. This is the ID that the external key store proxy uses to identify the external key.
@@ -1321,9 +1321,14 @@ declare namespace OpenSearch {
1321
1321
  * A description of the data source.
1322
1322
  */
1323
1323
  Description?: DataSourceDescription;
1324
+ /**
1325
+ * The status of the data source.
1326
+ */
1327
+ Status?: DataSourceStatus;
1324
1328
  }
1325
1329
  export type DataSourceList = DataSourceDetails[];
1326
1330
  export type DataSourceName = string;
1331
+ export type DataSourceStatus = "ACTIVE"|"DISABLED"|string;
1327
1332
  export interface DataSourceType {
1328
1333
  /**
1329
1334
  * An Amazon S3 data source.
@@ -2052,7 +2057,7 @@ declare namespace OpenSearch {
2052
2057
  */
2053
2058
  Endpoints?: EndpointsMap;
2054
2059
  /**
2055
- * The DualStack Hosted Zone Id for the domain.
2060
+ * The dual stack hosted zone ID for the domain.
2056
2061
  */
2057
2062
  DomainEndpointV2HostedZoneId?: HostedZoneId;
2058
2063
  /**
@@ -2318,6 +2323,10 @@ declare namespace OpenSearch {
2318
2323
  * A description of the data source.
2319
2324
  */
2320
2325
  Description?: DataSourceDescription;
2326
+ /**
2327
+ * The status of the data source response.
2328
+ */
2329
+ Status?: DataSourceStatus;
2321
2330
  }
2322
2331
  export interface GetDomainMaintenanceStatusRequest {
2323
2332
  /**
@@ -3579,6 +3588,10 @@ declare namespace OpenSearch {
3579
3588
  * A new description of the data source.
3580
3589
  */
3581
3590
  Description?: DataSourceDescription;
3591
+ /**
3592
+ * The status of the data source update request.
3593
+ */
3594
+ Status?: DataSourceStatus;
3582
3595
  }
3583
3596
  export interface UpdateDataSourceResponse {
3584
3597
  /**