| title | description | layout | subcategory | category |
|---|---|---|---|---|
AWS Incident Manager |
Basic information on our on-call scheduling and alerting tool |
article |
How To |
Team |
AWS Incident Manager provides on-call rotation scheduling and alerting for both automated and human generated events. It is our primary emergency notification system.
Access can be provided for any team member with an on-call or emergency notification
need. Ask in #login-platform-support and tag @login-platform-help if you need
access. See the Devops AWS Incident Manager wiki page
for more information on setup.
AWS Incident Manager is structured as follows:
- Contacts - Contacts are people who may be contacted for incident response.
- Schedules and Rotations - A rotation is made up of people. We organize our rotation membership by collecting users who will be part of the same set of on-call rotations and have the same on-call responsibilities.
- Escalation Plan - Each team should have an escalation policy which defines the order of notifications when an incident is routed to one or more rotations.
Integrations are configured for the following:
- CloudWatch - Allows CloudWatch Alarms to use SNS to raise an incident.
- NewRelic - Allows NewRelic to create Incident Manager incidents.
- Slack - Allows AWS Incident Manager to send alerts to Slack
- Devops AWS Incident Manager wiki page
- Ask in #login-platform-support if you have a problem with AWS Incident Manager.