

# Incident management in AMS Accelerate
<a name="acc-manage-incidents"></a>

In AMS Accelerate, you use the **AWS Support Center Console** to file incident reports. Incidents are AWS service performance issues that impact your managed environment, as determined by AMS Accelerate or you. Incidents identified by the AMS Accelerate team are first received as *events* (a change in system state captured by monitoring). If a configured threshold is breached, the event triggers an alarm, also called an alert. The AMS Accelerate operations team determines if the event is non-impacting, or an incident (a service interruption or degradation), or a problem (the underlying root cause of one or more incidents).

**Note**  
The AMS Accelerate team also receives incidents created by you programmatically using the [AWS Support API](https://docs.aws.amazon.com/awssupport/latest/user/Welcome.html) with service code `service-ams-operations-report-incident`.

For information about using Support, see [ Getting started with Support](https://docs.aws.amazon.com/awssupport/latest/user/getting-started.html).

# What is incident management?
<a name="what-is-incident-mgmt"></a>

Incident management is the process AMS uses to record, act on, communicate progress of, and provide notification of, active incidents.

The goal of the incident management process is to ensure that normal operation of your managed service is restored as quickly as possible, the business impact is minimized, and all concerned parties are kept informed.

Examples of incidents include (but are not restricted to) loss of or degradation of network connectivity, a non-responsive process or API, or a scheduled task not being performed (for example, a failed backup).

The following graphic depicts the workflow of an incident reported by you to AMS.

![\[Incident management workflow between AMS operations and the customer with a customer-reported incident.\]](http://docs.aws.amazon.com/managedservices/latest/accelerate-guide/images/incident-mgmt-workflow-customer.png)


This graphic depicts the workflow of an incident reported by AMS to you.

![\[Incident management workflow between AMS operations and the customer with a CloudWatch-detected incident.\]](http://docs.aws.amazon.com/managedservices/latest/accelerate-guide/images/incident-mgmt-workflow-ams.png)


## Incident priority
<a name="incident-priority"></a>

Incidents created in AWS Support center, console or Support API (SAPI), have different classifications than incidents created in the AMS console.
+ Low: Non-critical functions of your business service, or application, related to AWS or AMS resources are impacted.
+ Medium: A business service or application related to AWS and/or AMS resources is moderately impacted and is functioning in a degraded state.
+ High: Your business is significantly impacted. Critical functions of your application related to AWS and/or AMS resources are unavailable. Reserved for the most critical outages affecting production systems.

**Note**  
The AWS Support Console offers five levels of incident priority that we translate to the three AMS levels.

## How incident response and resolution work
<a name="acc-how-inc-work"></a>

AMS Accelerate uses IT service management (ITSM) incident management best practices to restore service, when needed, as quickly as possible.

We provide 24/7/365 follow-the-sun support through operations centers around the world with dedicated operators actively watching monitoring dashboards and incident queues.

Our operations engineers use internal incident tracking tools to identify, log, categorize, prioritize, diagnose, resolve, and close incidents; we provide you with updates on all of these activities through AWS Support Center and through the AWS Support API. Our operators leverage a variety of internal AWS support tools to help with all of those activities. These operators are deeply familiar with AMS Accelerate-supported infrastructure and have expert-level technical skills to address identified support issues. In the event our operators need assistance, the Premium Support and AWS service teams are available.

After your incident is received by the AMS Accelerate operations team, we validate the priority and classification working with you if there are any clarifications required. For example, if the incident report is better classified as a service request, it's reclassified and the AMS Accelerate service request team takes over and you're notified. If the incident can be resolved by the receiving operator, steps are taken to quickly resolve the incident. AMS Accelerate operators consult internal documentation for a resolution and, if needed, escalate the incident to other support resources until the incident is resolved. After it's resolved, the AMS Accelerate operations team documents the incident and resolution for future use.

In cases where critical severity incidents are impacting your critical workloads, AMS Accelerate may recommend an infrastructure restore. There is often a trade-off between troubleshooting an issue and simply restoring from a known functional backup, and your risks and impacts from service downtime are the deciding factors. If you have time to devote to troubleshooting issues, AMS Accelerate will assist you, and your cloud service delivery manager (CSDM) may get involved, but if the urgency to restore is high, AMS Accelerate can initiate a restore right away.

# Working with incidents in AMS Accelerate
<a name="working-with-incidents"></a>

From AWS Support Center, you can perform the following tasks:
+ Report and update an incident. To report an AMS Accelerate incident, choose **AMS Operations -- Report Incident** from the **Services** menu.
+ Get a list of, and detailed information about, all of your submitted incidents.
+ Narrow your search for incidents by status and other filters.
+ Add communications and file attachments to your incidents, and add email recipients for case correspondence.
+ Initiate a live chat or request a call back on your incident.
**Note**  
The live chat feature is not for security events; for security issues, create a high-priority (P1 or P2) support case.
+ Resolve incidents.
+ Rate incident communications.

The following examples describe using Support Center to submit an incident. After it's submitted, the AMS Accelerate team works with you to resolve the incident per the standard AMS Accelerate SLA.

# Submitting an incident for Accelerate
<a name="submitting-an-incident"></a>

To report an incident using Support Center, refer to the support documentation: [ Creating a support case](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case)

To report an incident using Support center:

1. Click **Create case**. The create incident case page opens.

1. Open the **Technical support issue type** menu and choose **AMS Operations -- Report Incident**. Supply information about your incident and choose **Create**.

1. To be kept informed by email at each step of the incident resolution process, be sure to fill in the **CC Emails** option; if you connect by federation, log in before following the link in the email that AMS Accelerate sends you about the incident.

**Note**  
Make your description as detailed as possible. Include relevant resource information, along with anything else that might help us understand your issue. For example, to troubleshoot performance, include timestamps and logs. For feature requests or general guidance questions, include a description of your environment and purpose. In all cases, follow the Description Guidance that appears on your case submission form.  
When you provide as much detail as possible, you increase the chances that your case can be resolved quickly.

You can also use the [AWS Support API](https://docs.aws.amazon.com/awssupport/latest/user/Welcome.html) with service code `service-ams-operations-report-incident` to report an incident.

# Monitoring and updating an Accelerate incident
<a name="mon-and-update-an-incident"></a>

You can update, monitor, and review incident reports and service requests, both called *cases*, by using Support Center, or programmatically using the Support API, [https://docs.aws.amazon.com/awssupport/latest/APIReference/API_DescribeCases.html](https://docs.aws.amazon.com/awssupport/latest/APIReference/API_DescribeCases.html) operation.

To monitor a case, incident or service request, using Support Center, follow these steps.

1. In the AWS Management console, browse to **Support**.

1. From the left navigation, select **Your support cases**, browse to a case and choose the **Subject** link to open a details page with current status and correspondences.

   If you want to use phone or chat at this point, click **Open case in Support Center** to open the case **Create** page in the Support Center, auto-populated with the AMS service type.

   When a reported incident or service request case is updated by the Accelerate operations team, you receive an email and a link to the incident in the Support Center so you can respond.
**Note**  
You can't respond to case correspondence by replying to the email.

   If there are many cases in the dashboard, you can use the **Filter** option:
   + **Subject**: Use this filter to search on keywords in the subject of the case.
   + **Severity**: Use this to filter cases by severity by selecting a severity from the list.
   + **Case type**: Use this to see all cases of a particular case type. Accelerate incidents and service requests appear under the Technical Support Case Type along with any service-specific cases.
   + **Status**: Use this to filter cases by status by selecting a specific status from the list.

1. To check the latest status, refresh the page.

1. If there are so many correspondences that they do not all appear on the page, choose **Load More**.

1. To provide an update to the case status, choose **Reply**, enter the new correspondence, and then choose **Submit**.

1. To close out the case after it has been resolved to your satisfaction, choose **Close case**.

   Be sure to rate the service through the 1-5 star rating to let AMS know how we're doing.

# Managing Accelerate incidents with the support API
<a name="managing-incidents-with-sapi"></a>

You can use the [Support API](https://docs.aws.amazon.com/awssupport/latest/user/Welcome.html) to create incidents and add correspondence with Support staff during investigations into your issues. The Support API models much of the behavior of the  [AWS Support Center](https://console.aws.amazon.com/support/home#/).

For information about you can use this AWS support service, see  [ Programming the Life of an AWS Support Case](https://docs.aws.amazon.com/awssupport/latest/user/Case_Life_Cycle.html#crebopbatecase).

**Note**  
The AMS Accelerate team receives incidents created by you programmatically using the with service code `service-ams-operations-report-incident`.

# Responding to an AMS Accelerate-generated incident
<a name="respond-ams-gen-incident"></a>

AMS Accelerate proactively monitors your resources. For more information, see  [Monitoring and event management in AMS Accelerate](acc-mon-event-mgmt.md). Sometimes AMS Accelerate identifies and creates an incident, most often to notify you of an event. If action on your part is required to resolve an incident, notification is sent by the AMS Accelerate team to the contact information you have provided for the account. You respond to this notification in the same way as for any other incident—usually through Support Center, though in some cases contact through email or phone is required.

**Important**  
To receive state change notifications for an incident case or service request, enter an email address in the addresses field. 

[![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/5ROuEwNSzSM/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/5ROuEwNSzSM)
