See: newUpdateIncidentRecord smart constructor.

Create a value of UpdateIncidentRecord with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

UpdateIncidentRecord, updateIncidentRecord_chatChannel - The Chatbot chat channel where responders can collaborate.

$sel:clientToken:UpdateIncidentRecord', updateIncidentRecord_clientToken - A token that ensures that the operation is called only once with the specified details.

UpdateIncidentRecord, updateIncidentRecord_impact - Defines the impact of the incident to customers and applications. Providing an impact overwrites the impact provided by the response plan.

Possible impacts:

• 1 - Critical impact, full application failure that impacts many to all customers.
• 2 - High impact, partial application failure with impact to many customers.
• 3 - Medium impact, the application is providing reduced service to customers.
• 4 - Low impact, customer aren't impacted by the problem yet.
• 5 - No impact, customers aren't currently impacted but urgent action is needed to avoid impact.

UpdateIncidentRecord, updateIncidentRecord_notificationTargets - The Amazon SNS targets that are notified when updates are made to an incident.

Using multiple SNS topics creates redundancy in the event that a Region is down during the incident.

UpdateIncidentRecord, updateIncidentRecord_status - The status of the incident. An incident can be Open or Resolved.

UpdateIncidentRecord, updateIncidentRecord_summary - A longer description of what occurred during the incident.

UpdateIncidentRecord, updateIncidentRecord_title - A brief description of the incident.

UpdateIncidentRecord, updateIncidentRecord_arn - The Amazon Resource Name (ARN) of the incident record you are updating.

The Chatbot chat channel where responders can collaborate.

A token that ensures that the operation is called only once with the specified details.

Defines the impact of the incident to customers and applications. Providing an impact overwrites the impact provided by the response plan.

Possible impacts:

• 1 - Critical impact, full application failure that impacts many to all customers.
• 2 - High impact, partial application failure with impact to many customers.
• 3 - Medium impact, the application is providing reduced service to customers.
• 4 - Low impact, customer aren't impacted by the problem yet.
• 5 - No impact, customers aren't currently impacted but urgent action is needed to avoid impact.

The Amazon SNS targets that are notified when updates are made to an incident.

Using multiple SNS topics creates redundancy in the event that a Region is down during the incident.

The status of the incident. An incident can be Open or Resolved.

A longer description of what occurred during the incident.

A brief description of the incident.

The Amazon Resource Name (ARN) of the incident record you are updating.

See: newUpdateIncidentRecordResponse smart constructor.

Create a value of UpdateIncidentRecordResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:httpStatus:UpdateIncidentRecordResponse', updateIncidentRecordResponse_httpStatus - The response's http status code.

The response's http status code.