AWS Elastic Block Store issues in one AZ in us-east-1

Re:AWS Elastic Block Store issues in one AZ in us-east-1 by jaytaylor on Sunday August 25, 2013 @04:54PM (#6273683)

This is the kind of thing you're susceptible to when you use AWS products that start with E: EBS, ELB, etc..

[ Parent | on HN ]

Re:AWS Elastic Block Store issues in one AZ in us-east-1 by nieksand on Sunday August 25, 2013 @05:18PM (#6273772)

At a minimum, you should use at least two availability zones if you care about high-availability on AWS. The vast majority of issues (including the current EBS hiccup) tend to be limited to one AZ.

For us, today's outage triggered a bunch of alerts, knocked 1/4 of our USE attribution servers offline (we're in four zones there) but otherwise caused no impact. Mostly just acked alerts and twiddled thumbs waiting for situation to resolve.

[ Parent | on HN ]

Re:AWS Elastic Block Store issues in one AZ in us-east-1 by gregr401 on Monday August 26, 2013 @01:11AM (#6275310)

No, this is the kind of thing that happens with a poor application architecture (ie, using one AZ). Sad that companies still can't get this right.

[ Parent | on HN ]

Re:AWS Elastic Block Store issues in one AZ in us-east-1 by mh- on Sunday August 25, 2013 @04:56PM (#6273689)

where's EC2 fall in that?

[ Parent | on HN ]

Re:AWS Elastic Block Store issues in one AZ in us-east-1 by weitzj on Sunday August 25, 2013 @05:20PM (#6273783)

if you want a safer EBS, create a raid ontop i and use snapshots.

[ Parent | on HN ]