Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

AWS is under-reporting the severity of the issue though. The primary outage may be in a single AZ, but there are parts of the AWS stack that affected all AZs in us-east-1, and potentially other regions as well. For example, even now I'm unable to create a new ElastiCache cluster in different AZs of us-east-1.


> I'm unable to create a new ElastiCache cluster in different AZs of us-east-1

Isn't that because Elasticache will distribute the cluster across AZs automatically?

https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/...


In this case, this was specifically with a single-AZ setup, using an AZ that was supposed to be unaffected.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: