Amazon Web Services Deployment The Right Way

Amazon Web Services Deployment The Right Way

In general, when considering all things “cloud” it’s healthy to retain a skeptical mind set and avoid succumbing to hype. But the fallout from the recent Amazon Web Services (AWS) outage is actually a very positive sign for Cloud Computing. Sure some sites got taken completely down, including a favorite of many, Quora. However, another popular site managed to survive the incident with comparatively minor hiccups: Netflix. This is the bright spot the cloud community should examine. As with many other leading websites, Keynote monitors the performance of certain transactions at According to Keynote measurements, on the east coast starting at 12am April 21st, Netflix’s performance for successful transactions stayed a consistent couple of seconds and was available 96% of the time. Granted this isn’t flawless execution, and note that the 27 failed data points are all timeouts resulting in just a red screen. However, compared to what happened to many sites, this is outstanding. (Y-axis details obscured.)

It’s not dumb luck that got Netflix off this easy. It’s the product of hard work and engineering time invested in building their Amazon Web Services deployment the right way. As Netflix has been touting in various cloud conferences this year, they’ve been forced to fully embrace AWS due to their tremendous growth. Basically, they only run credit card transactions in their private network. To ensure they always have enough capacity (and incidentally are highly available) they have turned provisioning decisions over to their operational systems. Whenever an Amazon instance is poorly performing they terminate it and get a new one. Likewise if there is an availability zone acting up (like what happened on April 21) then they automatically switch over to another.

This is how real high availability has always been done in networking: ensure that you can automatically failover to logically, physically, and geographically separate resources. Any real engineer will tell you that problems and failures will happen. Your availability track record is not based on how frequently this occurs but how gracefully you recover from them.

Herein is the promise of Cloud Computing: namely the favorable relationship between cost and failover capabilities. In a private network world you would have to build and pay for a lot of infrastructure yourself: multiple data centers, double the hardware, internet access connections on opposite sides of the building, etc. Very quickly the cost of high availability gets prohibitive, locking out all but the deepest of pockets. Netflix explicitly stated at Cloud Connect that, despite their growth, they just weren’t big enough to justify building a network of redundant data centers.

Enter Cloud Computing. Now having access to redundant data centers is just a matter of purchasing the right performance monitoring tools and the engineering time to program your applications and operational systems to take full advantage of on demand resources. In the end, you only pay for the infrastructure you use, not what you might need as is the case when doing it yourself. That’s the real shame and promise highlighted by this outage; young companies like Quora and Foursquare could easily have done just what Netflix has done. The barrier to entry here isn’t a huge budget but the knowledge and priorities to do the work. The next step of course after fully leveraging Amazon is to be able to failover to different cloud providers, and Netflix is probably working on exactly this, right now.

In a way this drives home a point we’ve known all along. Cloud Computing is not outsourcing; this implies a transfer of risk and responsibility. Your business, not Amazon or Microsoft or Google etc., are responsible for the performance of your applications whether they are in the cloud or not. Cloud Computing is a powerful tool to increase performance and availability many fold while reducing costs, if it’s used correctly. If you don’t use the tool properly then an outage isn’t Amazon’s fault, it’s yours. Amazon seems to agree: according to Gartner Analyst Lidya Leong this isn’t an outage that generates service credits. (Quote at very end of article.)

Contribution By Ian Withrow

Senior Product Manager
Keynote Systems, Inc.


Follow Us!


Established in 2009, is recognized as one of the leading authorities in cloud computing information. Most of the excellent CloudTweaks articles are provided by our own paid writers, with a small percentage provided by guest authors from around the globe, including CEOs, CIOs, Technology bloggers and Cloud enthusiasts. Our goal is to continue to build a growing community offering the best in-depth articles, interviews, event listings, whitepapers, infographics and much more...
Follow Us!

4 Responses to Amazon Web Services Deployment The Right Way

  1. […] Amazon Web Services Deployment the Right Way […]

  2. After we wrote this Amazon came out and decided to offer service credits anyway, just goes to show you the danger of making predictions or even repeating someone else’s. Although this may be more of a PR play than any particular contractual violations.

  3. Each region may then be divided into multiple availability zones. “By launching instances in separate Availability Zones,” Amazon says, “you can protect your applications from failure of a single location.” But today’s outage – which began around 1:41am Pacific time and also affected the use of Amazon’s Elastic Block Store (EBS) service – spread across multiple zones in the East region.

CloudTweaks Sponsors - Find out more!


Top Viral Impact

Cloud Infographic – The Future Of Big Data

Cloud Infographic – The Future Of Big Data

Cloud Infographic – The Future Of Big Data Big Data is BIG business and will continue to be one of the more predominant areas of focus in the coming years from small startups to large scale corporations. We’ve already covered on CloudTweaks how Big Data can be utilized in a number of interesting ways from preventing world hunger to…

Cloud Infographic: Most Used Cloud Apps

Cloud Infographic: Most Used Cloud Apps

Cloud app and analytics company, Netskope released its quarterly Cloud Report. The new report reveals that enterprise employees are using an average of 397 different cloud apps (most of which are unsanctioned), when IT estimated they have 40-50 — that’s a tenfold underestimation. Below is an infographic provided courtesy of the group at Netskope which goes into further detail.…

Cloud Infographic – Cyber Security And The New Frontier

Cloud Infographic – Cyber Security And The New Frontier

Cyber Security: The New Frontier The security environment of the 21st century is constantly evolving, and it’s difficult to predict where the next threats and dangers will come from. But one thing is clear: the ever-expanding frontier of digital space will continue to present firms and governments with security challenges. From politically-motivated Denial-of-Service attacks to…

Cloud Infographic – Cloud Fast Facts

Cloud Infographic – Cloud Fast Facts

Cloud Infographic – Cloud Fast Facts It’s no secret that Cloud Computing is more than just a buzz term as that ship has sailed off a long time ago. More and more companies are adopting the uses and benefits of cloud computing while aggressively factoring cloud services spending into their budget. Included is an excellent…

Established in 2009, CloudTweaks is recognized as one of the leading influencers in cloud computing, big data and internet of things (IoT) information. Our goal is to continue to build our growing information portal, by providing the best in-depth articles, interviews, event listings, whitepapers, infographics and much more.

You can help continue to support our community by social sharing, sponsoring, partnering or contributing to this great educational resource.


CloudTweaks Media
Phone: 1 (212) 763-0021

Join our newsletter