News for hackers. Stuff that matters.

A comment on Summary of the AWS Service Event in the Northern Virginia (US-East-1) Region. Parent comment

Re:Summary of the AWS Service Event in the Northern Virginia... by ashtonkem on Friday December 10, 2021 @08:41PM (#29517596)
If I recall there was a point in time where the control panel for all regions was in us-east-1. I seem to recall an outrage where the other regions were up, but you couldn’t change any resources because the management api was down in us-east-1
[ Parent | on HN ]
Re:Summary of the AWS Service Event in the Northern Virginia... by herodoturtle on Saturday December 11, 2021 @04:02AM (#29519556)
This was our exact experience with this outage.

Literally all our AWS resources are in EU/UK regions - and they all continued functioning just fine - but we couldn't sign in to our AWS console to manage said resources.

Thankfully the outage didn't impact our production systems at all, but our inability to access said console was quite alarming to say the least.

[ Parent | on HN ]
Re:Summary of the AWS Service Event in the Northern Virginia... by aaron42net on Saturday December 11, 2021 @10:59AM (#29521778)
The default region for global services including https://console.aws.amazon.com is us-east-1, but there are usual regional alternatives. For example: https://us-west-2.console.aws.amazon.com

It would probably be clearer that they exist if the console redirected to the regional URL when you switched regions.

STS, S3, etc have regional endpoints too that have continued to work when us-east-1 has been broken in the past and the various AWS clients can be configured to use them, which they also sadly don't tend to do by default.

[ Parent | on HN ]