Though they don’t disclose numbers, I’m very much interested in just how much data Amazon moves and stores through their web services. I think that because not only have they lowered prices, they’ve added new pricing tiers for moving over 5 PB of data.

Petabytes.

Crazy.

Anyways, starting July 1, new pricing for bandwidth goes into effect:

New data transfer price for US-Standard, US-West and Europe regions (effective July 1, 2011)

  • $0.000 – first 1 GB / month data transfer out
  • $0.120 per GB – up to 10 TB / month data transfer out (10 TB total)
  • $0.090 per GB – next 40 TB / month data transfer out (50TB total)
  • $0.070 per GB – next 100 TB / month data transfer out (150 TB total)
  • $0.050 per GB – next 350 TB / month data transfer out (500 TB total)
  • Contact us – next 524 TB / month data transfer out (1PB total)
  • Contact us – next 4 PB / month data transfer out (5PB total)
  • Contact us – data transfer out / month over 5 PB

According to Amazon, if you were moving 10TB in and 10TB out a month, your bill just went down 50%. Not bad.

CloudFront prices are also going down. For more specifics, visit the AWS Data Transfer Pricing Update detail page.

I’m sure you’ve either read about the Amazon Web Services outage of the weekend or visited a site that uses their architecture, such as Quora or Foursquare.

One part of their servers on demand product had issues – specifically their Elastic Block Storage product in one of their availability zones. Many servers use it for persistent storage, something the AWS EC2 product doesn’t offer by default. With these volumes being flaky, throwing errors or being office, many sites were in trouble.

The services that we use the most here at John Carroll, the Simple Storage Service (S3) and the Cloudfront content delivery network were not affected, thankfully, so I could enjoy the holiday weekend. I would have liked to play some online games on my PS3, but as you’ll see below, that too was off-line.

So what are some takeaways I see coming out of this outage?

First, don’t put all your eggs in one basket. SmugMug CEO Don MacAskill posted a very detailed blog post about the Amazon outage and how and why his company’s servers there weren’t affected. He says:

All of our services in AWS are spread across multiple Availability Zones (AZs). We’d use 4 if we could, but one of our AZs is capacity constrained, so we’re mostly spread across three. (I say “one of our” because your “us-east-1b” is likely different from my “us-east-1b” – every customer is assigned to different AZs and the names don’t match up). When one AZ has a hiccup, we simple use the other AZs. Often this is a graceful, but there can be hiccups – there are certainly tradeoffs.

Second, if you are going to leverage the cloud for services, and you should, you must have a backup plan or set of protocols for what to do if it hits the fan.

For example, if S3 did go down, our WordPress CMS would be affected, as we store user-uploaded assets in S3. To remedy that, we keep a local copy on our server, so our assets stay available to our site visitors. If S3 goes down, we can make a change to a plugin configuration and our assets will still be available. When S3 comes back online, we’d flip the switch and go back to serving things from the cloud.

Third, have a communication plan ready and keep users updated during the day.

The only spot I was finding out official information on the outage was on the AWS Service Health Dashboard, which is fine, that’s where it should be. In addition, many sites put up their own pages (Quora, Reddit come to mind) saying their were being affected by the outage.

If you have a blog, use it. Same goes for Twitter and Facebook. Amazon, even though the info was hidden, was good with updating exactly what was going on and where they were in the process of getting services back online. For example:

Apr 24, 5:05 AM PDT: As detailed in previous updates, the vast majority of affected EBS volumes have been restored by this point, and we are working through a more time-consuming recovery process for remaining volumes. We have made steady progress on this front over the past few hours. If your volume is among those recently recovered, it should be accessible and usable without additional action.

Good information that’s being updated often is important to help keep customers in the loop. Compare that to Sony, who’s Playstation network has been offline since last Wednesday. Their updates have been nebulous, at best. On April 21, they posted on their official blog:

While we are investigating the cause of the Network outage, we wanted to alert you that it may be a full day or two before we’re able to get the service completely back up and running.

The last update given by the company, on April 23, said this:

We sincerely regret that PlayStation Network and Qriocity services have been suspended, and we are working around the clock to bring them both back online. Our efforts to resolve this matter involve re-building our system to further strengthen our network infrastructure. Though this task is time-consuming, we decided it was worth the time necessary to provide the system with additional security.

We thank you for your patience to date and ask for a little more while we move towards completion of this project. We will continue to give you updates as they become available.

And then, silence. It’s now Monday morning in the US and the service is not online and the current status/ETA for being online hasn’t been updated since Saturday. IGN has more on Sony’s PR response to this outage.

That type of communication wouldn’t work on our campuses. Part of your planning must be a communications plan for who is responsible for keeping a certain audience up to date on the status of services.

My colleagues at Allegheny are doing it right this morning. They had a power outage over the weekend and took to their intranet to update the campus community, on a Sunday.

Screen+shot+2011 04 25+at+10 49 47+AM

Am I going to stop using Amazon’s cloud services over this outage? No, definitely not. Is this going to make Amazon improve the service? Yes. Is this a sucky way to do it? Of course.

I’ll be updating this post with feedback from other higher ed web and marketing folks. Andrew Careaga has some interesting thoughts on the outage looking at it through a lens of education.

We use Wufoo a ton here at John Carroll – it was one of the first things I signed us up for when I got there a little over a year ago and it’s taken the campus by storm.

Where there was previously no good way for people to do forms, registrations and feedback online (except for, ugh, SurveyMonkey), they now create all sorts of forms for our on and off campus audiences and process payments through it as well. It has saved me a ton of work over the last year, and for that I’m grateful. In fact, just last month we used it to do all the fundraising for our campus community radio station. It worked like a charm.

Two things that are cool about Wufoo are that forms you create there are hosted securely and that you can create your own themes and CSS to style your forms to match the look and feel of your institution. One of the ways to do this is to add in your logo to appear at the top of your forms. Ours looks like this:

Wufoo

I’m hosting that image in our account over at Amazon S3. In Wufoo’s theme creator, I listed the image as:

http://webmedia.jcu.edu/images/JCU_logo4.gif

That CNAME points to our S3 bucket. The image worked fine and looked great on our theme.

The only problem with doing it that way is that it makes the form unsecure. Chrome showed me this:

Insecure

After doing a bit of research, I was glad to see that you can, in fact, serve secure files from Amazon S3. The catch is that you cannot use a CNAME to access your files – you have to use Amazon’s domain name. Instead of using the URL above, to get secure files from S3, you have to structure your URL as so:

https://s3.amazonaws.com/webmedia.jcu.edu/images/JCU_logo4.gif

See, that was easy. Now my images and other files coming from S3 can be secure, if needed. Since the change, the form has been showing as completely secure.

Secure