4 ms·
It is absolutely affecting more than one availability zone. Just because people didn't lose boxes outside of one AZ doesn't mean there weren't service disruptio
by freerobby 14y ago
It is absolutely affecting more than one availability zone. Just because people didn't lose boxes outside of one AZ doesn't mean there weren't service disruptions outside of it. I know multiple people, myself included, who STILL cannot launch new instances anywhere in US-East. The EC2 web console and API have also been down intermittently and throwing errors for hours.
- xtractinator 14y ago1 out of my 6 instances in the region was affected. It took me about an hour to get it back up (which was me clicking once and waiting). I wonder how much of that is fallout from instances being sent to other availability zones and bottle-necking.
- rlpb 14y agoIf one availability zone is down, there will be suddenly be ton of extra people trying to start new instances in the other availability zones. Could there just be a shortage of available instances in the other availability zones? Perhaps Amazon don't keep enough spare capacity for this eventuality (nor would I expect them to)?
- datasage 14y agoThis certainly can happen. You can't rely on being able to launch enough replacement instances if a zone fails. You can at least mitigate it by keeping utilization of your instances below what would be needed to handle load of one zone failing. I suspect to save money, many people are pushing utilization as high as possible.
- sofuture 14y agoThis is what reserved instances are for. You can by low use reserved instances for disaster planning.
- anothermachine 14y agoIf an outage in one zone causes a brownout in the other zones, then the aren't independent "availability" zones in any logical sense. They may as well be on the same power supply.
- ars 14y agoThey are independent IF you buy them in advance. If you wait till an actual outage then it's too late.