|
|
|
|
|
by coreyw
3237 days ago
|
|
This is exactly why you should design your services to run in multiple availability zones to mitigate issues like this. We run our most critical services in at least 3 availability zones and we are moving the rest of our services soon as well. While these problems are unfortunate, it is part of relying on Amazon to manage resources. Always plan for service degradation and look for ways to mitigate against issues like this. |
|
Not very helpful when Redshift didn't have a single note in their status page for 30+ minutes after it went down.
Any bets on whether the status page will show up as Red for EC2/Redshift tomorrow? I'll take 100 to 1 odds for $1 that it won't be red.