Commentary

John Foley
Editor, InformationWeek  

Amazon's Cloud Is Too Cloudy

Amazon senior VP Andy Jassy talks about Amazon Web Services in a recent interview with TechFlash.com. It's an interesting chat with the guy who oversees Amazon's cloud computing business. Unfortunately, Jassy, once again, refuses to answer key questions about AWS.

Amazon senior VP Andy Jassy talks about Amazon Web Services in a recent interview with TechFlash.com. It's an interesting chat with the guy who oversees Amazon's cloud computing business. Unfortunately, Jassy, once again, refuses to answer key questions about AWS.Jassy is the influential executive who came up with the business model behind AWS five years ago, and the public-facing personalities of AWS -- Amazon CTO Werner Vogels and VP Adam Selipsky, in particular -- report to him. As the brains behind AWS, Jassy is one of the more interesting, yet underexposed personalities, in the IT industry.

So I was glad to see the interview with TechFlash, as it presented an opportunity to learn more about Amazon's groundbreaking IT service model. In the Q&A, Jassy talks about enterprise adoption of AWS, service level agreements, and how he and a group of buddies get together every month to scarf down chicken wings at the Wingdome.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But Jassy clams up when asked about the size of AWS and future plans.

TechFlash: How many people work in Web services?

Jassy: We don't disclose how many people are in the business, but I will tell you we have a significant, meaningful, talented team working on this. And if you look at what's happened over the last year or two in terms of what the team has delivered, you can tell it's not a team of 10 people.

And later, this:

TechFlash: Does Amazon use containerized data centers?

Jassy: We don't disclose that.

All of this hemming and hawing by Amazon is getting tiresome. When I interviewed Jassy last November for InformationWeek's feature story on Werner Vogels, Jassy talked at length about the strategy behind AWS, but he declined to reveal info on the size of the business. "We don't break out the revenue and the financials of AWS," he told me.

What we've got here is an IT services company that refuses to disclose where its data centers are located, how it plans to build new data centers, how many people it employs in that part of its business, how much revenue it brings in, or how fast it's growing. It teases with references to enterprise customers, but won't say how many it has or, in many cases, who they are.

As I pointed out in a post a few days ago, Amazon is growing in influence in the IT industry, having struck agreements with IBM, Microsoft, Oracle, Red Hat, and Sun in the past 12 months. As Amazon's reach expands, its reticence becomes a bigger issue. How can IT pros, with confidence, turn over their IT workloads to a service provider that provides such limited visibility into its core operations?

I'm not the only one asking these questions. In a Jan. 16 Webcast to discuss Amazon's fourth quarter 2008 financial results, the first question to be asked, by a financial analyst, had to with Amazon's cloud computing partnership with Capgemini. Wall Street obviously wants to know more about AWS, too (here's my breakdown of the numbers, "Amazon Web Services Help Fuel Blow-Out Quarter.")

I've said it before, and I'll say it again: If Amazon is serious about the enterprise market, it's going to have to get more granular in the information it makes available on AWS.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links