Summary of the AWS Service Event in the Northern Virginia (US-East-1) Region

Re:Summary of the AWS Service Event in the Northern Virginia... by gkop on Friday December 10, 2021 @08:55PM (#29517675)

At the large platform company where I work, our policy is if the customer reported the issue before our internal monitoring caught it, we have failed. Give 5 minutes for alerting lag, 10 minutes to evaluate the magnitude of impact, 10 minutes to craft the content and get it approved, 5 minutes to execute the update, adds up to 30 minutes end to end with healthy buffer at each step.

1 hour (52 minutes according to the article) sounds meh. I wonder what their error rate and latency graphs look like from that day.

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by Aperocky on Friday December 10, 2021 @09:11PM (#29517764)

> our policy is if the customer reported the issue before our internal monitoring caught it

They've discovered it right away, the Service Health Dashboard was not updated. source: link.

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by gkop on Friday December 10, 2021 @09:39PM (#29517921)

They don’t say explicitly right away do they? I skimmed twice.

But yes you’re right, there’s no reason to question their monitoring or alerting specifically.

[ Parent | on HN ]