News for hackers. Stuff that matters.
Re:Lessons We’ve Learned Using AWS (2010) by skyisblue on Thursday March 02, 2017 @01:37AM (#13772023)
What happens when multiple regions on AWS are down? Would it be a good idea to also have a complete backup infrastructure on another cloud service?
Re:Lessons We’ve Learned Using AWS (2010) by Johnny555 on Thursday March 02, 2017 @02:35AM (#13772299)
At my company, we've decided that if multiple AWS regions are down, we're down too.

We use so many AWS services that porting to a second cloud provider is cost-prohibitive at this point. So we're willing to accept that if 2 USA regions and one European region are down, we're down too.

Re:Lessons We’ve Learned Using AWS (2010) by npolet on Thursday March 02, 2017 @05:25AM (#13773047)
> At my company, we've decided that if multiple AWS regions are down, we're down too.

We've come to the same conclusion as well. We cannot afford the engineering hours to run duplicate infrastructure just in case the big boys go down.

If multiple AWS regions go down... we wait until they are not down. Our developers sighed in relief when we decided that this was going to be our course of action... but we're approaching the scale that requires us to really mitigate against large scale outages like this. For now we bury our heads.

Re:Lessons We’ve Learned Using AWS (2010) by edaemon on Thursday March 02, 2017 @01:42AM (#13772048)
I think it's best to keep your critical infrastructure portable. It usually doesn't make financial sense to have a hot backup on another cloud service but having a plan to quickly switch it over in case of emergency is a good idea.

For example, using something like Terraform could spin up infrastructure on AWS, but in a pinch you could make your templates work for Google, Azure, etc.

That said, if your infrastructure is at all complex it can be very difficult to keep it portable.

Re:Lessons We’ve Learned Using AWS (2010) by Erwin on Thursday March 02, 2017 @04:13AM (#13772742)
Do you know of any known public example of someone who has actually done that? This seems advise similar to eating 6 portions vegetables a day: everyone says it's critical, nobody is doing it.

In all the cases of Amazon and Google Cloud outages I've seen that were beyond a single zone, it all hit the high-valued companies hard. I've never seen anyone declare that they decided to activate their alternative provider where they have a continuously updated copy of all the data so the data loss is minimal.

Everyone is just assuming Amazon or Google will fix it and that any data loss from activating a non-hot standby is not worth it.

Re:Lessons We’ve Learned Using AWS (2010) by edaemon on Thursday March 02, 2017 @01:22PM (#13776669)
I don't know of any public examples where someone made an emergency switch from one provider to another. I doubt it's happened often, mostly because multi-region failures are so rare. Like I said, if your infrastructure is at all complex it's very difficult to keep it portable. I doubt any "high-value" company would be able to make an emergency switch without their downtime exceeding what they would have experienced if they just stayed put.
Re:Lessons We’ve Learned Using AWS (2010) by nickpsecurity on Thursday March 02, 2017 @06:22AM (#13773296)
There's products on the market dedicated to abstracting clouds for using more than one or switching easily. I'd be shocked if there weren't companies using them for the former. Those most concerned with availability usually just avoid clouds, though.
Re:Lessons We’ve Learned Using AWS (2010) by samhamilton on Thursday March 02, 2017 @05:45AM (#13773120)
I believe wix.com does this, a mix of AWS and Google Cloud. Can't find the blog post where they listed out how they achieved it