Category: Amazon EC2*


S3 for Static Web Content

In Userscript.org and Amazon S3, Jesse Andrews describes how he moved all of his static content from his own server over to S3. Jesse set up the virtual hosting, moved over all of the content (using S3 Fox no less), and had everything up and running inside of 15 minutes. As he notes “it took longer to write this post than it did to do the conversion.”

Userscripts.org isn’t some quiet site with little or no traffic. As the primary repository for Greasemonkey scripts, it is quite busy — Jesse says that they handled 24 million requests for 307GB of static content in the last two months alone.

Jesse asked his friends to try out the new version side-by-side with the old one. In this unscientific and somewhat subjective test, the new version (using S3) was unanimously judged to be faster.

By the way, be sure to browse the items tagged with Amazon on the site. You’ll find my old favorite Book Burro (also written by Jesse) and lots of other cool stuff.

 

But wait, there’s more!

Casey Muller wrote a really nice guide, including code for an s3commit script (to copy assets to S3) on Serving the Rails Public Directory out of S3. Casey is one of the developers of jamglue, currently in beta and serving up its content from S3.

— Jeff;

EC2 Rock and Roll

There’s so much happening with Amazon EC2 that I can hardly read it all. Here’s a sampling:

  • The Atlantis Computing blog talks about Amazin Amazon or why EC2 is the bee’s knees. Instead of investing between 30 and 40% of their seed capital on hardware, they have implemented it on top of EC2. As the post notes, the monetary savings is important, but it is not the only benefit to them. They can now focus on their core competency of building their application (Thewebtop).
  • One-time Amazonian Greg Linden, author of the Geeking with Greg blog, talks discusses the use of Hadoop on Amazon EC2. Greg saved me the trouble of linking to the Hadoop on EC2 page.
  • Speaking of Hadoop on EC2, Scott Delap says that you can Run Your Own Google Style Computing Cluster with Hadoop and Amazon EC2.
  • The Android Tech blog says that we are Leading the Charge to Web 3.0.  As they say, “Who knew?”
  • David Berlind (co-organizer of Mashup Camp and Startup Camp) does the math, in Amazons Jeff Bezos: Honey, I Just Shrunk the Server Hosting Business. David really cuts to the chase of what makes EC2 special, when he writes “None of these back of the envelope calculations take into account what happens if you get smart about server utilization and decide to take full advantage of the Amazon APIs that, in a blink of an eye, can turn these x86 instances on and off. With dedicated hosting of the sort that we have, because of our annual contract, we’re married to two servers for an entire year. Whether we’re using them or not, we’re paying. Not so with Amazon’s EC2.”

If that’s not enough for you, check out the AWS Buzz items for EC2 on del.icio.us.

— Jeff;

ElasticLive – Hershey’s Kisses

KissAn important part of our mission as Web Services Evangelists is to encourage our developer community to innovate. We invite them to surprise us with new and interesting ways to consume our services, to show us the Power of Innovation !

One such innovation is running Windows Server 2003 on an Amazon EC2 instance. The power of Windows combined with the elasticity of Amazon EC2  – Just like Hershey’s Kisses (Attractive on the Outside, Nourishing in the Inside).

The tech pundits at Enomaly have put 2 & 2 together by leveraging their experience with Amazon EC2 and successfully installed Windows Server 2003 on an Amazon EC2 instance using QEMU. QEMU is an open source processor emulator allowing a user to simulate a complete computer system within another one. This screenshot shows that they were able to connect to Amazon EC2 instance via remote desktop  connection. Pretty Cool!

They have also put together a small how-to article for others. It will be very interesting to see some real benchmarking on how this emulation layer affects performance.

What is ElasticLive?  ElasticLive is a value-added service on top of Amazon EC2.  Power of Amazon EC2 combined with their expertise and professional support. Pre-installed, pre-configured, automatically-updating applications on the top of web-scale platform at your disposal. What else do you need?

–Jinesh

A New ISV Business Model

Amazon Elastic Compute Cloud continues to impress the people who matter most: software developers (in this instance, an ISV).

Genexus is an innovative software platform that enables non-technical business people to rapidly build out applications–including an online presence. Andres Aguiar, their chief architect, sent me a note yesterday to say “We have GXPortal running in EC2. It took us one day to make it work. The site is running a beta of the next GXPortal version, on Java/MySQL”.

There’s an exciting new business opportunity for ISVs: create software that enables businesses to run in an environment without a dedicated data center! In essence, an environment where you throw your servers away! It’s a bit different than the traditional ASP model that has been around for a while now, in that the customer has total control over (and is responsible for) their own server; however they do get to eliminate all that muck known as the expense and hassle of a physical data center. It’s highly unlikely that any business will be able to operate their own center for less than $0.10 per hour!

— Mike

ASP.Net Code Sample – ECS Custom Control in C#

As mentioned in the previous post, we have been working with our friends at Microsoft to create some additional code samples for .Net and ECS. Here is sample code for an ASP.Net custom control which uses version 4 of ECS. The control is written in C#. Refer to the README file for more information and complete step-by-step directions on how to make use of the code.

Updated ECS 4 Release

We rolled out a new set of bits for ECS 4 early this morning. Here are the release notes:

Features and Fixes

  1. For JP only, there are some changes to Marketplace-related operations:
    1. For SellerListingLookup using IdType=Listing, Seller Id is now a required parameter. The REST syntax for passing in Seller Id is “SellerId=“.
    2. SellerListingSearch now requires Seller Id as a parameter. The REST syntax for passing in Seller Id is “SellerId=“.
    3. SearchIndex is now an optional parameter to MarketPlaceSearch since “Marketplace” is the only supported index in JP. Users are not required to pass in SearchIndex since ECS always defaults to “Marketplace”.
    4. The Keywords, ShipOption, Country, BrowseNode, PostalCode, Sort (-bfp) and OfferStatus input parameters are not supported. If supplied, these parameters will be ignored and SellerListingSearch will return all Marketplace Listings for the SellerId in the request.
    5. The QuantityAllocated, ConditionNote, FeaturedCategory, Storeid and Storename output elements are never returned by SellerListingSearch.
  2. SellerListingLookup is now supported for (JP/FR/CA) for idType=Exchange
  3. Seller Ratings are now supported, for the US locale only. The SellerLookup operation will now return correct Seller Ratings.
  4. all ECS 4.0 operations that return Offers will now return correct Seller/AverageFeedbackRating,
    Seller/TotalFeedback, Seller/TotalFeedbackPages, and Seller/SellerFeedback/Feedback/Rating values.

Operational Changes

XSLT requests sent to the amazon domains (amazon.com, amazon.fr, amazon.ca, amazon.co.uk, amazon.de, and amazon.co.jp) will now be redirected to the appropriate sub-domain of amznxslt.com. Users should modify their applications to make direct reference to the appropriate sub-domain:

  • xml-us.amznxslt.com
  • xml-jp.amznxslt.com
  • xml-de.amznxslt.com
  • xml-uk.amznxslt.com
  • xml-fr.amznxslt.com
  • xml-ca.amznxslt.com

Known Issues

  1. Customer reviews returned by search operations may not be in-sync with the reviews on the web sites.
  2. SellerListingLookup by ListingId is not returning any results (US, UK, and DE).

Updated ECS 3 Release

We rolled out a new set of bits for ECS 3 early this morning. Here are the release notes:

Features and Fixes

  1. For JP only, there are some changes to Marketplace-related operations:
    1. SellerSearch and ExchangeSearch are now supported except for the ExchangeQuantityAllocated and ExchangeFeaturedCategory elements.
    2. MarketplaceSearch now requires the Seller Id to be passed in as a required parameter. The REST syntax for passing in Seller Id is “seller-id=“.
    3. index is now an optional parameter to MarketPlaceSearch since “marketplace” is the only supported index in JP. Users are not required to pass in index since ECS always defaults to “marketplace”.
    4. The following MarketplaceSearch input parameters are not supported: keyword-search=title or keyword-search=titledesc, geo, area-id, browse-id, zipcode, sort=-bfp. These will be ignored and MarketplaceSearch will return all Marketplace Listings for the SellerId in the request.
    5. The ExchangeQuantityAllocated and ExchangeFeaturedCategory output elements (in ListingProductDetails) are never returned by the MarketplaceSearch.
  2. ExchangeSearch is now supported for the JP, FR, and CA locales.
  3. Seller Ratings are now supported (US locale only). All Search operations that return ThirdPartyProductDetails are now returning the correct SellerRating.
  4. Search operations now support SellerId and SellerNickname for Amazon’s offer in ThirdPartyProductDetails.
  5. In the FR locale, the ExchangePrice in MarketplaceSearch is now correctly formatted. In the previous release the ExchangePrice was incorrectly formatted as EUR 9.99 instead of EUR 9,99.
  6. In previous releases, some responses contained invalid control characters. The control characters are now properly encoded.

Operational Changes

XSLT requests sent to the amazon domains (amazon.com, amazon.fr, amazon.ca, amazon.co.uk, amazon.de, and amazon.co.jp) will now be redirected to the appropriate sub-domain of amznxslt.com. Users should modify their applications to make direct reference to the appropriate sub-domain:

  • xml-us.amznxslt.com
  • xml-jp.amznxslt.com
  • xml-de.amznxslt.com
  • xml-uk.amznxslt.com
  • xml-fr.amznxslt.com
  • xml-ca.amznxslt.com

Known Issues

  1. Customer reviews returned by search operations may not be in-sync with the reviews on the web sites.
  2. SellerListingLookup by ListingId is not returning any results (US, UK, and DE).