cdk-lambda-subminute 2.0.377 → 2.0.378

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.
@@ -42,7 +42,9 @@
42
42
  "phoneNumber"
43
43
  ],
44
44
  "members": {
45
- "phoneNumber": {}
45
+ "phoneNumber": {
46
+ "shape": "S9"
47
+ }
46
48
  }
47
49
  },
48
50
  "output": {
@@ -131,7 +133,9 @@
131
133
  "PhoneNumber"
132
134
  ],
133
135
  "members": {
134
- "PhoneNumber": {},
136
+ "PhoneNumber": {
137
+ "shape": "So"
138
+ },
135
139
  "LanguageCode": {}
136
140
  }
137
141
  },
@@ -195,7 +199,9 @@
195
199
  "PhoneNumber"
196
200
  ],
197
201
  "members": {
198
- "PhoneNumber": {}
202
+ "PhoneNumber": {
203
+ "shape": "So"
204
+ }
199
205
  }
200
206
  },
201
207
  "output": {
@@ -405,7 +411,9 @@
405
411
  "CreatedAt": {
406
412
  "type": "timestamp"
407
413
  },
408
- "PhoneNumber": {},
414
+ "PhoneNumber": {
415
+ "shape": "S9"
416
+ },
409
417
  "Status": {},
410
418
  "Iso2CountryCode": {},
411
419
  "RouteType": {},
@@ -432,7 +440,9 @@
432
440
  "members": {
433
441
  "phoneNumbers": {
434
442
  "type": "list",
435
- "member": {}
443
+ "member": {
444
+ "shape": "S9"
445
+ }
436
446
  },
437
447
  "nextToken": {}
438
448
  }
@@ -487,7 +497,9 @@
487
497
  "member": {
488
498
  "type": "structure",
489
499
  "members": {
490
- "PhoneNumber": {},
500
+ "PhoneNumber": {
501
+ "shape": "So"
502
+ },
491
503
  "Status": {}
492
504
  }
493
505
  }
@@ -587,7 +599,9 @@
587
599
  "phoneNumber"
588
600
  ],
589
601
  "members": {
590
- "phoneNumber": {}
602
+ "phoneNumber": {
603
+ "shape": "S9"
604
+ }
591
605
  }
592
606
  },
593
607
  "output": {
@@ -605,7 +619,9 @@
605
619
  "members": {
606
620
  "TopicArn": {},
607
621
  "TargetArn": {},
608
- "PhoneNumber": {},
622
+ "PhoneNumber": {
623
+ "shape": "S9"
624
+ },
609
625
  "Message": {},
610
626
  "Subject": {},
611
627
  "MessageStructure": {},
@@ -883,7 +899,9 @@
883
899
  "OneTimePassword"
884
900
  ],
885
901
  "members": {
886
- "PhoneNumber": {},
902
+ "PhoneNumber": {
903
+ "shape": "So"
904
+ },
887
905
  "OneTimePassword": {}
888
906
  }
889
907
  },
@@ -895,11 +913,19 @@
895
913
  }
896
914
  },
897
915
  "shapes": {
916
+ "S9": {
917
+ "type": "string",
918
+ "sensitive": true
919
+ },
898
920
  "Sj": {
899
921
  "type": "map",
900
922
  "key": {},
901
923
  "value": {}
902
924
  },
925
+ "So": {
926
+ "type": "string",
927
+ "sensitive": true
928
+ },
903
929
  "St": {
904
930
  "type": "map",
905
931
  "key": {},
@@ -12,11 +12,11 @@ declare class ConnectParticipant extends Service {
12
12
  constructor(options?: ConnectParticipant.Types.ClientConfiguration)
13
13
  config: Config & ConnectParticipant.Types.ClientConfiguration;
14
14
  /**
15
- * Allows you to confirm that the attachment has been uploaded using the pre-signed URL provided in StartAttachmentUpload API. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
15
+ * Allows you to confirm that the attachment has been uploaded using the pre-signed URL provided in StartAttachmentUpload API. A conflict exception is thrown when an attachment with that identifier is already being uploaded. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
16
16
  */
17
17
  completeAttachmentUpload(params: ConnectParticipant.Types.CompleteAttachmentUploadRequest, callback?: (err: AWSError, data: ConnectParticipant.Types.CompleteAttachmentUploadResponse) => void): Request<ConnectParticipant.Types.CompleteAttachmentUploadResponse, AWSError>;
18
18
  /**
19
- * Allows you to confirm that the attachment has been uploaded using the pre-signed URL provided in StartAttachmentUpload API. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
19
+ * Allows you to confirm that the attachment has been uploaded using the pre-signed URL provided in StartAttachmentUpload API. A conflict exception is thrown when an attachment with that identifier is already being uploaded. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
20
20
  */
21
21
  completeAttachmentUpload(callback?: (err: AWSError, data: ConnectParticipant.Types.CompleteAttachmentUploadResponse) => void): Request<ConnectParticipant.Types.CompleteAttachmentUploadResponse, AWSError>;
22
22
  /**
@@ -52,19 +52,19 @@ declare class ConnectParticipant extends Service {
52
52
  */
53
53
  getAttachment(callback?: (err: AWSError, data: ConnectParticipant.Types.GetAttachmentResponse) => void): Request<ConnectParticipant.Types.GetAttachmentResponse, AWSError>;
54
54
  /**
55
- * Retrieves a transcript of the session, including details about any attachments. For information about accessing past chat contact transcripts for a persistent chat, see Enable persistent chat. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
55
+ * Retrieves a transcript of the session, including details about any attachments. For information about accessing past chat contact transcripts for a persistent chat, see Enable persistent chat. If you have a process that consumes events in the transcript of an chat that has ended, note that chat transcripts contain the following event content types if the event has occurred during the chat session: application/vnd.amazonaws.connect.event.participant.left application/vnd.amazonaws.connect.event.participant.joined application/vnd.amazonaws.connect.event.chat.ended application/vnd.amazonaws.connect.event.transfer.succeeded application/vnd.amazonaws.connect.event.transfer.failed ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
56
56
  */
57
57
  getTranscript(params: ConnectParticipant.Types.GetTranscriptRequest, callback?: (err: AWSError, data: ConnectParticipant.Types.GetTranscriptResponse) => void): Request<ConnectParticipant.Types.GetTranscriptResponse, AWSError>;
58
58
  /**
59
- * Retrieves a transcript of the session, including details about any attachments. For information about accessing past chat contact transcripts for a persistent chat, see Enable persistent chat. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
59
+ * Retrieves a transcript of the session, including details about any attachments. For information about accessing past chat contact transcripts for a persistent chat, see Enable persistent chat. If you have a process that consumes events in the transcript of an chat that has ended, note that chat transcripts contain the following event content types if the event has occurred during the chat session: application/vnd.amazonaws.connect.event.participant.left application/vnd.amazonaws.connect.event.participant.joined application/vnd.amazonaws.connect.event.chat.ended application/vnd.amazonaws.connect.event.transfer.succeeded application/vnd.amazonaws.connect.event.transfer.failed ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
60
60
  */
61
61
  getTranscript(callback?: (err: AWSError, data: ConnectParticipant.Types.GetTranscriptResponse) => void): Request<ConnectParticipant.Types.GetTranscriptResponse, AWSError>;
62
62
  /**
63
- * Sends an event. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
63
+ * The application/vnd.amazonaws.connect.event.connection.acknowledged ContentType will no longer be supported starting December 31, 2024. This event has been migrated to the CreateParticipantConnection API using the ConnectParticipant field. Sends an event. Message receipts are not supported when there are more than two active participants in the chat. Using the SendEvent API for message receipts when a supervisor is barged-in will result in a conflict exception. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
64
64
  */
65
65
  sendEvent(params: ConnectParticipant.Types.SendEventRequest, callback?: (err: AWSError, data: ConnectParticipant.Types.SendEventResponse) => void): Request<ConnectParticipant.Types.SendEventResponse, AWSError>;
66
66
  /**
67
- * Sends an event. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
67
+ * The application/vnd.amazonaws.connect.event.connection.acknowledged ContentType will no longer be supported starting December 31, 2024. This event has been migrated to the CreateParticipantConnection API using the ConnectParticipant field. Sends an event. Message receipts are not supported when there are more than two active participants in the chat. Using the SendEvent API for message receipts when a supervisor is barged-in will result in a conflict exception. ConnectionToken is used for invoking this API instead of ParticipantToken. The Amazon Connect Participant Service APIs do not use Signature Version 4 authentication.
68
68
  */
69
69
  sendEvent(callback?: (err: AWSError, data: ConnectParticipant.Types.SendEventResponse) => void): Request<ConnectParticipant.Types.SendEventResponse, AWSError>;
70
70
  /**
@@ -352,7 +352,7 @@ declare namespace ConnectParticipant {
352
352
  export type ScanDirection = "FORWARD"|"BACKWARD"|string;
353
353
  export interface SendEventRequest {
354
354
  /**
355
- * The content type of the request. Supported types are: application/vnd.amazonaws.connect.event.typing application/vnd.amazonaws.connect.event.connection.acknowledged application/vnd.amazonaws.connect.event.message.delivered application/vnd.amazonaws.connect.event.message.read
355
+ * The content type of the request. Supported types are: application/vnd.amazonaws.connect.event.typing application/vnd.amazonaws.connect.event.connection.acknowledged (will be deprecated on December 31, 2024) application/vnd.amazonaws.connect.event.message.delivered application/vnd.amazonaws.connect.event.message.read
356
356
  */
357
357
  ContentType: ChatContentType;
358
358
  /**
@@ -397,13 +397,21 @@ declare class EMR extends Service {
397
397
  */
398
398
  setKeepJobFlowAliveWhenNoSteps(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
399
399
  /**
400
- * SetTerminationProtection locks a cluster (job flow) so the Amazon EC2 instances in the cluster cannot be terminated by user intervention, an API call, or in the event of a job-flow error. The cluster still terminates upon successful completion of the job flow. Calling SetTerminationProtection on a cluster is similar to calling the Amazon EC2 DisableAPITermination API on all Amazon EC2 instances in a cluster. SetTerminationProtection is used to prevent accidental termination of a cluster and to ensure that in the event of an error, the instances persist so that you can recover any data stored in their ephemeral instance storage. To terminate a cluster that has been locked by setting SetTerminationProtection to true, you must first unlock the job flow by a subsequent call to SetTerminationProtection in which you set the value to false. For more information, seeManaging Cluster Termination in the Amazon EMR Management Guide.
400
+ * SetTerminationProtection locks a cluster (job flow) so the Amazon EC2 instances in the cluster cannot be terminated by user intervention, an API call, or in the event of a job-flow error. The cluster still terminates upon successful completion of the job flow. Calling SetTerminationProtection on a cluster is similar to calling the Amazon EC2 DisableAPITermination API on all Amazon EC2 instances in a cluster. SetTerminationProtection is used to prevent accidental termination of a cluster and to ensure that in the event of an error, the instances persist so that you can recover any data stored in their ephemeral instance storage. To terminate a cluster that has been locked by setting SetTerminationProtection to true, you must first unlock the job flow by a subsequent call to SetTerminationProtection in which you set the value to false. For more information, see Managing Cluster Termination in the Amazon EMR Management Guide.
401
401
  */
402
402
  setTerminationProtection(params: EMR.Types.SetTerminationProtectionInput, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
403
403
  /**
404
- * SetTerminationProtection locks a cluster (job flow) so the Amazon EC2 instances in the cluster cannot be terminated by user intervention, an API call, or in the event of a job-flow error. The cluster still terminates upon successful completion of the job flow. Calling SetTerminationProtection on a cluster is similar to calling the Amazon EC2 DisableAPITermination API on all Amazon EC2 instances in a cluster. SetTerminationProtection is used to prevent accidental termination of a cluster and to ensure that in the event of an error, the instances persist so that you can recover any data stored in their ephemeral instance storage. To terminate a cluster that has been locked by setting SetTerminationProtection to true, you must first unlock the job flow by a subsequent call to SetTerminationProtection in which you set the value to false. For more information, seeManaging Cluster Termination in the Amazon EMR Management Guide.
404
+ * SetTerminationProtection locks a cluster (job flow) so the Amazon EC2 instances in the cluster cannot be terminated by user intervention, an API call, or in the event of a job-flow error. The cluster still terminates upon successful completion of the job flow. Calling SetTerminationProtection on a cluster is similar to calling the Amazon EC2 DisableAPITermination API on all Amazon EC2 instances in a cluster. SetTerminationProtection is used to prevent accidental termination of a cluster and to ensure that in the event of an error, the instances persist so that you can recover any data stored in their ephemeral instance storage. To terminate a cluster that has been locked by setting SetTerminationProtection to true, you must first unlock the job flow by a subsequent call to SetTerminationProtection in which you set the value to false. For more information, see Managing Cluster Termination in the Amazon EMR Management Guide.
405
405
  */
406
406
  setTerminationProtection(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
407
+ /**
408
+ * Specify whether to enable unhealthy node replacement, which lets Amazon EMR gracefully replace core nodes on a cluster if any nodes become unhealthy. For example, a node becomes unhealthy if disk usage is above 90%. If unhealthy node replacement is on and TerminationProtected are off, Amazon EMR immediately terminates the unhealthy core nodes. To use unhealthy node replacement and retain unhealthy core nodes, use to turn on termination protection. In such cases, Amazon EMR adds the unhealthy nodes to a denylist, reducing job interruptions and failures. If unhealthy node replacement is on, Amazon EMR notifies YARN and other applications on the cluster to stop scheduling tasks with these nodes, moves the data, and then terminates the nodes. For more information, see graceful node replacement in the Amazon EMR Management Guide.
409
+ */
410
+ setUnhealthyNodeReplacement(params: EMR.Types.SetUnhealthyNodeReplacementInput, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
411
+ /**
412
+ * Specify whether to enable unhealthy node replacement, which lets Amazon EMR gracefully replace core nodes on a cluster if any nodes become unhealthy. For example, a node becomes unhealthy if disk usage is above 90%. If unhealthy node replacement is on and TerminationProtected are off, Amazon EMR immediately terminates the unhealthy core nodes. To use unhealthy node replacement and retain unhealthy core nodes, use to turn on termination protection. In such cases, Amazon EMR adds the unhealthy nodes to a denylist, reducing job interruptions and failures. If unhealthy node replacement is on, Amazon EMR notifies YARN and other applications on the cluster to stop scheduling tasks with these nodes, moves the data, and then terminates the nodes. For more information, see graceful node replacement in the Amazon EMR Management Guide.
413
+ */
414
+ setUnhealthyNodeReplacement(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
407
415
  /**
408
416
  * The SetVisibleToAllUsers parameter is no longer supported. Your cluster may be visible to all users in your account. To restrict cluster access using an IAM policy, see Identity and Access Management for Amazon EMR. Sets the Cluster$VisibleToAllUsers value for an Amazon EMR cluster. When true, IAM principals in the Amazon Web Services account can perform Amazon EMR cluster actions that their IAM policies allow. When false, only the IAM principal that created the cluster and the Amazon Web Services account root user can perform Amazon EMR actions on the cluster, regardless of IAM permissions policies attached to other IAM principals. This action works on running clusters. When you create a cluster, use the RunJobFlowInput$VisibleToAllUsers parameter. For more information, see Understanding the Amazon EMR Cluster VisibleToAllUsers Setting in the Amazon EMR Management Guide.
409
417
  */
@@ -796,6 +804,10 @@ declare namespace EMR {
796
804
  * Indicates whether Amazon EMR will lock the cluster to prevent the Amazon EC2 instances from being terminated by an API call or user intervention, or in the event of a cluster error.
797
805
  */
798
806
  TerminationProtected?: Boolean;
807
+ /**
808
+ * Indicates whether Amazon EMR should gracefully replace Amazon EC2 core instances that have degraded within the cluster.
809
+ */
810
+ UnhealthyNodeReplacement?: BooleanObject;
799
811
  /**
800
812
  * Indicates whether the cluster is visible to IAM principals in the Amazon Web Services account associated with the cluster. When true, IAM principals in the Amazon Web Services account can perform Amazon EMR cluster actions on the cluster that their IAM policies allow. When false, only the IAM principal that created the cluster and the Amazon Web Services account root user can perform Amazon EMR actions, regardless of IAM permissions policies attached to other IAM principals. The default value is true if a value is not provided when creating a cluster using the Amazon EMR API RunJobFlow command, the CLI create-cluster command, or the Amazon Web Services Management Console.
801
813
  */
@@ -2273,6 +2285,10 @@ declare namespace EMR {
2273
2285
  * Specifies whether to lock the cluster to prevent the Amazon EC2 instances from being terminated by API call, user intervention, or in the event of a job-flow error.
2274
2286
  */
2275
2287
  TerminationProtected?: Boolean;
2288
+ /**
2289
+ * Indicates whether Amazon EMR should gracefully replace core nodes that have degraded within the cluster.
2290
+ */
2291
+ UnhealthyNodeReplacement?: BooleanObject;
2276
2292
  /**
2277
2293
  * Applies only to Amazon EMR release versions earlier than 4.0. The Hadoop version for the cluster. Valid inputs are "0.18" (no longer maintained), "0.20" (no longer maintained), "0.20.205" (no longer maintained), "1.0.3", "2.2.0", or "2.4.0". If you do not set this value, the default of 0.18 is used, unless the AmiVersion parameter is set in the RunJobFlow call, in which case the default version of Hadoop for that AMI version is used.
2278
2294
  */
@@ -2355,6 +2371,10 @@ declare namespace EMR {
2355
2371
  * Specifies whether the Amazon EC2 instances in the cluster are protected from termination by API calls, user intervention, or in the event of a job-flow error.
2356
2372
  */
2357
2373
  TerminationProtected?: Boolean;
2374
+ /**
2375
+ * Indicates whether Amazon EMR should gracefully replace core nodes that have degraded within the cluster.
2376
+ */
2377
+ UnhealthyNodeReplacement?: BooleanObject;
2358
2378
  /**
2359
2379
  * The Hadoop version for the cluster.
2360
2380
  */
@@ -3361,6 +3381,16 @@ declare namespace EMR {
3361
3381
  */
3362
3382
  TerminationProtected: Boolean;
3363
3383
  }
3384
+ export interface SetUnhealthyNodeReplacementInput {
3385
+ /**
3386
+ * The list of strings that uniquely identify the clusters for which to turn on unhealthy node replacement. You can get these identifiers by running the RunJobFlow or the DescribeJobFlows operations.
3387
+ */
3388
+ JobFlowIds: XmlStringList;
3389
+ /**
3390
+ * Indicates whether to turn on or turn off graceful unhealthy node replacement.
3391
+ */
3392
+ UnhealthyNodeReplacement: BooleanObject;
3393
+ }
3364
3394
  export interface SetVisibleToAllUsersInput {
3365
3395
  /**
3366
3396
  * The unique identifier of the job flow (cluster).