So AWS is having trouble again. I am a huge public cloud advocate, BUT if you don't diversify not just with other public clouds, but with on-premise as well you are asking for it.
In 2016, I wrote about this on my blog http://tuxlabs.com/?p=430 it's not just availability people should worry about.
some interesting effects on IoT
> I thought I couldn't vacuum because us-east1 was down, but it turns out that my drive filled up and dhclient couldn't write to resolv.conf and so actually it was just that DNS wasn't working -- https://twitter.com/mjg59/status/1331703327692709888
> My fucking doorbell doesn't work because AWS us-east-1 is having issues -- https://twitter.com/SJP1804/status/1331643504443928578
> Half the internet running on one company's infrastructure is a major national security issue, both with gov cloud and civilian cloud. And these are accidents..... -- https://twitter.com/r0wdy_/status/1331694152937996289
> An Amazon AWS outage is currently impacting our iRobot Home App. Please know that our team is aware and monitoring the situation and hope to get the App back online soon. Thank you for your understanding and patience. -- https://twitter.com/iRobot/status/1331667670383685635
> huge outage on many AWS Services: Kinesis is experiencing increased API errors in the US-EAST-1 Region. This is also causing issues with Amplify, API Gateway, AppStream2, AppSync, Athena, Cloudformation, Cloudtrail, Cloudwatch, Cognito, DynamoDB, IoT Services -- https://twitter.com/victorlazari/status/1331634362937438211
So, only us-east1 is down. If you have app running active-active over multi regions, it should be okay, right?
Here is the aws Dashboard: https://status.aws.amazon.com/
Does AWS write-up what caused these issues when it's finally resolved? Would be interesting to know what takes down so many servers.
Alexa skills and Amazon Music down too. CloudWatch erratic. Seems like a big one.
Again! We have a lot of problems from AWS outages https://hackernoon.com/moving-to-the-cloud-doesnt-prevent-ou...