Skip to content

Commit 977796e

Browse files
author
awstools
committed
docs(client-ssm-contacts): Doc-only updates for Incident Manager Contacts August 2025
1 parent 6c73c89 commit 977796e

File tree

4 files changed

+64
-25
lines changed

4 files changed

+64
-25
lines changed

clients/client-ssm-contacts/src/commands/DeleteContactChannelCommand.ts

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,11 @@ export interface DeleteContactChannelCommandInput extends DeleteContactChannelRe
2828
export interface DeleteContactChannelCommandOutput extends DeleteContactChannelResult, __MetadataBearer {}
2929

3030
/**
31-
* <p>To no longer receive engagements on a contact channel, you can delete the channel from a
32-
* contact. Deleting the contact channel removes it from the contact's engagement plan. If you
33-
* delete the only contact channel for a contact, you won't be able to engage that contact
34-
* during an incident.</p>
31+
* <p>To stop receiving engagements on a contact channel, you can delete the channel from a
32+
* contact. Deleting the contact channel does not remove it from the contact's engagement
33+
* plan, but the stage that includes the channel will be ignored. If you delete the only
34+
* contact channel for a contact, you'll no longer be able to engage that contact during an
35+
* incident.</p>
3536
* @example
3637
* Use a bare-bones client and the command you need to make an API call.
3738
* ```javascript

clients/client-ssm-contacts/src/commands/DeleteContactCommand.ts

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,11 @@ export interface DeleteContactCommandInput extends DeleteContactRequest {}
2828
export interface DeleteContactCommandOutput extends DeleteContactResult, __MetadataBearer {}
2929

3030
/**
31-
* <p>To remove a contact from Incident Manager, you can delete the contact. Deleting a contact
32-
* removes them from all escalation plans and related response plans. Deleting an escalation
33-
* plan removes it from all related response plans. You will have to recreate the contact and
34-
* its contact channels before you can use it again.</p>
31+
* <p>To remove a contact from Incident Manager, you can delete the contact. However, deleting a
32+
* contact does not remove it from escalation plans and related response plans. Deleting an
33+
* escalation plan also does not remove it from all related response plans. To modify an
34+
* escalation plan, we recommend using the <a>UpdateContact</a> action to specify a
35+
* different existing contact.</p>
3536
* @example
3637
* Use a bare-bones client and the command you need to make an API call.
3738
* ```javascript

clients/client-ssm-contacts/src/commands/ListTagsForResourceCommand.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ export interface ListTagsForResourceCommandInput extends ListTagsForResourceRequ
2828
export interface ListTagsForResourceCommandOutput extends ListTagsForResourceResult, __MetadataBearer {}
2929

3030
/**
31-
* <p>Lists the tags of an escalation plan or contact.</p>
31+
* <p>Lists the tags of a contact, escalation plan, rotation, or on-call schedule.</p>
3232
* @example
3333
* Use a bare-bones client and the command you need to make an API call.
3434
* ```javascript

clients/client-ssm-contacts/src/models/models_0.ts

Lines changed: 53 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -330,8 +330,8 @@ export interface ChannelTargetInfo {
330330
ContactChannelId: string | undefined;
331331

332332
/**
333-
* <p>The number of minutes to wait to retry sending engagement in the case the engagement
334-
* initially fails.</p>
333+
* <p>The number of minutes to wait before retrying to send engagement if the engagement
334+
* initially failed.</p>
335335
* @public
336336
*/
337337
RetryIntervalInMinutes?: number | undefined;
@@ -455,8 +455,21 @@ export interface Contact {
455455
DisplayName?: string | undefined;
456456

457457
/**
458-
* <p>Refers to the type of contact. A single contact is type <code>PERSONAL</code> and an
459-
* escalation plan is type <code>ESCALATION</code>.</p>
458+
* <p>The type of contact.</p>
459+
* <ul>
460+
* <li>
461+
* <p>
462+
* <code>PERSONAL</code>: A single, individual contact.</p>
463+
* </li>
464+
* <li>
465+
* <p>
466+
* <code>ESCALATION</code>: An escalation plan.</p>
467+
* </li>
468+
* <li>
469+
* <p>
470+
* <code>ONCALL_SCHEDULE</code>: An on-call schedule.</p>
471+
* </li>
472+
* </ul>
460473
* @public
461474
*/
462475
Type: ContactType | undefined;
@@ -601,13 +614,13 @@ export interface CoverageTime {
601614
*/
602615
export interface Target {
603616
/**
604-
* <p>Information about the contact channel Incident Manager is engaging.</p>
617+
* <p>Information about the contact channel that Incident Manager engages.</p>
605618
* @public
606619
*/
607620
ChannelTargetInfo?: ChannelTargetInfo | undefined;
608621

609622
/**
610-
* <p>Information about the contact that Incident Manager is engaging.</p>
623+
* <p>Information about the contact that Incident Manager engages.</p>
611624
* @public
612625
*/
613626
ContactTargetInfo?: ContactTargetInfo | undefined;
@@ -692,8 +705,21 @@ export interface CreateContactRequest {
692705
DisplayName?: string | undefined;
693706

694707
/**
695-
* <p>To create an escalation plan use <code>ESCALATION</code>. To create a contact use
696-
* <code>PERSONAL</code>.</p>
708+
* <p>The type of contact to create.</p>
709+
* <ul>
710+
* <li>
711+
* <p>
712+
* <code>PERSONAL</code>: A single, individual contact.</p>
713+
* </li>
714+
* <li>
715+
* <p>
716+
* <code>ESCALATION</code>: An escalation plan.</p>
717+
* </li>
718+
* <li>
719+
* <p>
720+
* <code>ONCALL_SCHEDULE</code>: An on-call schedule.</p>
721+
* </li>
722+
* </ul>
697723
* @public
698724
*/
699725
Type: ContactType | undefined;
@@ -968,14 +994,15 @@ export interface RecurrenceSettings {
968994

969995
/**
970996
* <p>The number of contacts, or shift team members designated to be on call concurrently
971-
* during a shift. For example, in an on-call schedule containing ten contacts, a value of
997+
* during a shift. For example, in an on-call schedule that contains ten contacts, a value of
972998
* <code>2</code> designates that two of them are on call at any given time.</p>
973999
* @public
9741000
*/
9751001
NumberOfOnCalls: number | undefined;
9761002

9771003
/**
978-
* <p>Information about the days of the week included in on-call rotation coverage.</p>
1004+
* <p>Information about the days of the week that the on-call rotation coverage
1005+
* includes.</p>
9791006
* @public
9801007
*/
9811008
ShiftCoverages?: Partial<Record<DayOfWeek, CoverageTime[]>> | undefined;
@@ -999,6 +1026,11 @@ export interface CreateRotationRequest {
9991026

10001027
/**
10011028
* <p>The Amazon Resource Names (ARNs) of the contacts to add to the rotation.</p>
1029+
* <note>
1030+
* <p>Only the <code>PERSONAL</code> contact type is supported. The contact types
1031+
* <code>ESCALATION</code> and <code>ONCALL_SCHEDULE</code> are not supported for this
1032+
* operation. </p>
1033+
* </note>
10021034
* <p>The order that you list the contacts in is their shift order in the rotation schedule.
10031035
* To change the order of the contact's shifts, use the <a>UpdateRotation</a>
10041036
* operation.</p>
@@ -1019,7 +1051,7 @@ export interface CreateRotationRequest {
10191051
* Database</a> on the IANA website.</p>
10201052
* <note>
10211053
* <p>Designators for time zones that don’t support Daylight Savings Time rules, such as
1022-
* Pacific Standard Time (PST) and Pacific Daylight Time (PDT), are not supported.</p>
1054+
* Pacific Standard Time (PST), are not supported.</p>
10231055
* </note>
10241056
* @public
10251057
*/
@@ -1445,7 +1477,7 @@ export interface GetContactResult {
14451477
DisplayName?: string | undefined;
14461478

14471479
/**
1448-
* <p>The type of contact, either <code>PERSONAL</code> or <code>ESCALATION</code>.</p>
1480+
* <p>The type of contact.</p>
14491481
* @public
14501482
*/
14511483
Type: ContactType | undefined;
@@ -1719,8 +1751,7 @@ export interface ListContactsRequest {
17191751
AliasPrefix?: string | undefined;
17201752

17211753
/**
1722-
* <p>The type of contact. A contact is type <code>PERSONAL</code> and an escalation plan is
1723-
* type <code>ESCALATION</code>.</p>
1754+
* <p>The type of contact.</p>
17241755
* @public
17251756
*/
17261757
Type?: ContactType | undefined;
@@ -2510,7 +2541,8 @@ export interface ListRotationShiftsResult {
25102541
*/
25112542
export interface ListTagsForResourceRequest {
25122543
/**
2513-
* <p>The Amazon Resource Name (ARN) of the contact or escalation plan.</p>
2544+
* <p>The Amazon Resource Name (ARN) of the contact, escalation plan, rotation, or on-call
2545+
* schedule.</p>
25142546
* @public
25152547
*/
25162548
ResourceARN: string | undefined;
@@ -2769,6 +2801,11 @@ export interface UpdateRotationRequest {
27692801

27702802
/**
27712803
* <p>The Amazon Resource Names (ARNs) of the contacts to include in the updated rotation. </p>
2804+
* <note>
2805+
* <p>Only the <code>PERSONAL</code> contact type is supported. The contact types
2806+
* <code>ESCALATION</code> and <code>ONCALL_SCHEDULE</code> are not supported for this
2807+
* operation. </p>
2808+
* </note>
27722809
* <p>The order in which you list the contacts is their shift order in the rotation
27732810
* schedule.</p>
27742811
* @public
@@ -2788,7 +2825,7 @@ export interface UpdateRotationRequest {
27882825
* Database</a> on the IANA website.</p>
27892826
* <note>
27902827
* <p>Designators for time zones that don’t support Daylight Savings Time Rules, such as
2791-
* Pacific Standard Time (PST) and Pacific Daylight Time (PDT), aren't supported.</p>
2828+
* Pacific Standard Time (PST), aren't supported.</p>
27922829
* </note>
27932830
* @public
27942831
*/

0 commit comments

Comments
 (0)