{ "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://raw.githubusercontent.com/api-evangelist/amazon-incident-manager/refs/heads/main/json-schema/incident-manager-start-incident-input-schema.json", "title": "StartIncidentInput", "description": "StartIncidentInput schema", "type": "object", "properties": { "clientToken": { "allOf": [ { "$ref": "#/components/schemas/ClientToken" }, { "description": "A token ensuring that the operation is called only once with the specified details." } ] }, "impact": { "allOf": [ { "$ref": "#/components/schemas/Impact" }, { "description": "
Defines the impact to the customers. Providing an impact overwrites the impact provided by a response plan.
Possible impacts:
1 - Critical impact, this typically relates to 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 might aren't impacted by the problem yet.
5 - No impact, customers aren't currently impacted but urgent action is needed to avoid impact.