{"id":303,"date":"2009-03-26T14:39:11","date_gmt":"2009-03-26T21:39:11","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/cqtwo\/?p=303"},"modified":"2009-04-02T17:40:30","modified_gmt":"2009-04-03T00:40:30","slug":"amazon-cloud-computing-support","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/2009\/03\/26\/amazon-cloud-computing-support\/","title":{"rendered":"Amazon Cloud Computing Support"},"content":{"rendered":"

Amazon continues to roll out cloud computing offerings at a blistering rate.\u00a0 Today, they just announced a toolkit<\/a> for Eclipse<\/a>, the open source IDE.\u00a0 I’ve been playing around a bit with S3<\/a>, their storage service, and EC2<\/a>, their virtual server offering (although I wish that they would offer SLES<\/a> in addition to OpenSUSE<\/a>.)\u00a0 They also have a database<\/a> and a content distribution network<\/a>.\u00a0 Not bad for a bookstore.<\/p>\n

I recently talked to a friend about building out their data center and my immediate response was, “Why on earth would you want to build a data center?”\u00a0 Of course, there are still good reasons but there are fewer and fewer of them each day.<\/p>\n

<\/p>\n

One of the advantages of rolling your own physical data center is that you get to establish relationships with lovely vendors, like Novell.\u00a0 You set up support agreements and we charge you for them; if something breaks, we’ll be on the phone or in person helping you fix it.\u00a0 There’s different levels of this kind of break\/fix support: we can put teams of engineers full-time at your data centers around the world, or we can give you a part-time person that you share with a half-dozen other customers.\u00a0 That way, they know what’s going on in your specific environment and you have a person you rely on rather than some phone bank; sharing the resource, obviously, is cheaper.\u00a0 There’s also off-site (remote) options with access to a named engineer who’s only available by phone, or direct access to specialists (L2 or backline in the jargon).\u00a0 And so on down the list to regular 24×7 phone support; it’s a full menu<\/a>.<\/p>\n

I think Novell has very, very good support.\u00a0 But what does Amazon’s support look like?<\/p>\n

They offer Premium Support<\/a> <\/em>in addition to forums, FAQs, and a dashboard.\u00a0 There are two levels of premium support\u00a0 Gold gives you 24×7 phone support, so it’s really the only option for serious enterprise-class customers.\u00a0 (Silver gives you 12×5 access to their trouble-ticketing system.)\u00a0 But Gold really only gives you what is termed in the industry “Level 1” support; the frontline help desk personnel who are charged with answering the majority of (sometimes inane) questions.\u00a0 If they determine that you’ve got a real problem that is beyond their abilities, you get ‘escalated’ to Level 2, a level populated by real nerds with specialized skills in particular technologies.\u00a0 Level 1 does the triage, handles the first aid, and sends hard cases to specialists.\u00a0 (Level 3, then, does bug fixes to the code to solve problems that aren’t resolved in L1\/L2.\u00a0 There is no Level 4, and sometimes the L1\/L2\/L3 distinctions get blurry; our L2 teams, for example, often write code that designated “L3” teams review and approve.)<\/p>\n

So Amazon’s support at the moment is limited to what I would consider the most basic break\/fix offering, even at their Gold level.\u00a0 At $4,800\/yr. (and up) with no annual contract, though, it’s cheap by enterprise standards, and is available for all of their software services.<\/p>\n

But in the world of software (and software as a service) support, there’s a distinction between response and resolution.\u00a0 The Amazon Gold support is a response-time service level.\u00a0 That is, they commit to responding <\/em>to your request in a specified time.\u00a0 They do not commit to resolving that issue in a specified time.\u00a0 Their response time service levels are one hour for high severity service requests with Gold support; normal is one business day.\u00a0 (At least, I think that’s right — the terms are a bit unclear; I don’t understand the difference between what they call “high severity” and “urgent.”)<\/p>\n

More later.<\/p>\n","protected":false},"excerpt":{"rendered":"

Amazon continues to roll out cloud computing offerings at a blistering rate.\u00a0 Today, they just announced a toolkit for Eclipse, the open source IDE.\u00a0 I’ve been playing around a bit with S3, their storage service, and EC2, their virtual server … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1116,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1424,27],"tags":[],"class_list":["post-303","post","type-post","status-publish","format-standard","hentry","category-enterprise-web-20","category-governance"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8jQA6-4T","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/posts\/303","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/users\/1116"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/comments?post=303"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/posts\/303\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/media?parent=303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/categories?post=303"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/tags?post=303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}