事件已经结束接下来该怎么办？.pdf

1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Giorgio Bonfiglio(he/him)Principal TAMEnterprise SupportAmazon Web ServicesAnthony Bush(he/him)Pri

2、ncipal EngineerEvent EngineeringAmazon Web ServicesThe incident is over:Now what?C O P 2 1 6 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Who we are 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Event management at AWS Conducting effective retrospectives Le

3、arning&evolving at scaleAgenda 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Phase 1:Detect&mitigate 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Service-driven Metrics Synthetic monitoring

4、Aggregate AlarmsCustomer-driven Traffic anomalies Impact reportsDetect 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Detect:Top-level dashboard 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.S

5、ingle service eventsTriggered by service alarmsEngage:Service team Others as required AWS SupportEngageMulti-service eventsTriggered by aggregate alarmsEngage:AWS Incident Response AWS Support Impacted services The“usual suspects”2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Tec

6、h callInvestigation and recovery Participants:Service teams,service leadership Goal:Resolve the issueCoordinateSupport callCommunications and guidance Participants:Support and service leadership Goal:Help customers recover 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazo